We'd like to submit a configurable connector to OneLogin like Github's connector. (ref: the attached image)
However, I couldn't understand how to submit such the request though I've read https://developers.onelogin.com/saml/app-catalog
How can we allow users to edit custom values in Configuration tab?
a screenshot of Github Connector's Configuration tab
EDITED
I've understood what information to be submitted for a non-configurable connector by reading the document. However, nothing mentioned a configurable connector.
So I'd like to know:
How to submit a configurable connector
A format of a configurable connector request
Sorry for omitting the context. OneLogin's web page led me to ask them questions in StackOverflow so I've assumed those who will answer to my question are OneLogin's members.
The unique way to request a new connector to be added to the OneLogin catalog is by submitting a support ticket.
Related
So I have gone in details through the Jobs XML documentation.
The steps that I completed are :
Creating a recruitment manager to post and retrieve jobs.
Created a url for Facebook to crawl job xml data referring this.
My question refers to application-callback-url section in the xml which specifies to configure an endpoint to receive applications received from facebook in raw json data.
Question
I don't want to receive applications from Facebook but rather want to redirect the user to a particular ATS where the applicant can proceed with their application. It should be Apply on Website and not just Apply when I post jobs. This is where all the necessary information needs to be present but I couldn't find anything relevant to my use case.
There are 2 endpoints /me/jobs and /me/job_feeds. I am not understanding the difference between the 2 and which one should I be using as per my use case?
I don't mind if you use an example from another API that is not Adobe Analytics'. I just need to know the pattern that I have to follow in order to succesfully convert a Postman request into a NiFi request.
After successfully creating requests to pull reports from Adobe Analytics via Postman, I´m having difficulties to migrate these Postman requests to NiFi. I haven´t been able to find concrete use cases that explicity explain how to do this kind of task step-by-step.
I'm trying to build a backend on top of NiFi to handle multiple data extracts from Adobe Analytics in an efficient and robust way. That is instead of having to create all required scripts by myself. Yet, there is more documentation about REST APIs and Postman cases than there is about REST APIs and NiFi cases.
In the screenshot below we can see how the Postman request looks like. It takes 3 headers and 1 temporary header that includes the authorization value (Bearer token). This temporary header is generated automatically after filling in the OAuth 2.0 authorization form in the Authorization tab, as shown here.
Then, we have the body of the request. This json text is generated automatically by debugging Adobe Analytics' workspaces as shown here.
I'd like to know the following in a step-by-step manner with screenshots if possible:
Which processor(s) should I use in NiFi to obtain a similar response as the one I got in Postman?
Which properties should I add/remove from the processor to make this work?
How should I name these properties?
Is there a default property whose value/name I should modify?
As you can see, the question mainly refers to properties setup in NiFi, as well as Processor selection. I already tried to configure some processors but I don't seem to get the correct properties setup, or maybe I'm selecting the wrong processors.
I'm using NiFi v1.6.0 and Postman v7.8.0
This is most likely an easy task for users already familiar with NiFi and API requests, but it has proven challenging to me. Hopefully this will help other users looking to build more robust pipelines by using NiFi instead of doing it manually.
Thanks.
It only takes 3 NiFi processors to replicate a REST API request that works in Postman. In this solution we use a request that contains a nested JSON request. The advantage of this simple approach is that it reduces the amount of configuration required to obtain a successful response from the API. That is, even if you are using a complex JSON request. In this case the body of the JSON request is passed through the GenerateFlowFile processor, without the need of any other processor to parse/format the request.
Step #1. Create a processor called GenerateFlowFile. The only property that you will have to modify is the Custom Text. Paste in there your whole JSON request just as it was in Postman. In this case I'm using the very same JSON shown in the question above. It's a good idea to setup Yield Duration to 10 seconds or more.
Step #2. Create a processor called InvokeHTTP. Then modify the 6 properties shown in the screenshots below. Use the same Authorization details you've used in Postman. Make sure to copy the Bearer token from Postman after it has been tested. Also, don't forget to setup the HTTP Method, Remote URL and Content-Type as well.
Step #3. Finally, add a couple of LogAttribute processors to store the output of InvokeHTTP. One of these LogAttribute processors should store successful responses. The other one can be used for Failure, Original, Retry and No-Retry. Or you can create LogAttribute for each of these outputs.
Step #4. Now, connect the processors and Start your data flow! You should start seeing data populate the Successful LogAttribute. Then you can use the Data Provenance option to review the incoming data and confirm that this is exactly the same result you previously obtained from Postman.
Note: This is a simple, straightforward, "for starters" solution to replicate a Postman API request using a nested static JSON. There are more solutions in StackOverflow that tackle more complex cases, like dynamic JSON. Here's a list of some other posts:
nifi invokehttp post complex json
In NiFi processor 'InvokeHTTP' where do you write body of POST request?
Configuring HTTP POST request from Nifi
I can easily view user sessions in Jira by accessing System > Security > User Sessions (see documentation here).
However, I can not find a similiar option in Confluence. Is it possible to access the user sessions in Confluence?
In the end, I would like to access it programmatically but I am afraid that if there is not even a way to get there via the UI, I am out of luck doing so via the Confluence API.
The question was asked here already, but there was no satisfying answer.
Thanks!
You can use the Confluence User List macro (confluence server):
https://confluence.atlassian.com/confeap/user-list-macro-480346630.html?_ga=2.138789171.1460206440.1517834060-1884022569.1490585845
Don't forget to enable the User Log In Listener module as described in the instructions of the link I shared above to be able to see online/offline users.
As for an API way, I don't think there is a way to do this at the moment. You can try and find a way to build your own plugin that extends the listener module used by the above macro if that is even possible.
I have successfully posted data to IBM Connections using the X-LConn-RunAs Header in my API calls to create Activity Stream Entries, Blog Posts, Wiki Pages, Forum Entries and File Uploads on behalf of someone else although it is not documented in some of the APIs. The only API that does not seem to support this Header is the Activity API. Here is what I did:
I added my technical user to the "trustedExternalApplication" role in the "WidgetContainer" application.
I added my technical user to the "admin" role in all other applications.
I added the X-LConn-RunAs Header to my api call like this: X-LConn-RunAs: userid=D2A7325-...
I made sure the referenced user exists in IBM Connections.
I sent my call to: http://myconnections/activities/service/atom2/activity?activityUuid=GH765...
The post is still being created with the technical user as creator instead of the user referenced by X-LConn-RunAs. I tested this against my on premises IBM Connections 5.0 installation as well as IBM Connections Cloud. While all other API calls support this Header the Activities don't.
Did anybody have more luck than myself and figured out how to use it or is there another way to achieve the same result with a different header or some additional information in the message body? I tried to send an <author> element but that is being ignored as it says in the documentation.
As just heard in an IBM Connect 16 session (you are sitting left of me ;-) ), as of today Impersonation of activity stream and status update data is not possible
I have a GWT screen in which i have a file upload bar,whenever i attach something and click send,the request should go on server side which in turn logs an JIRA request with attachment as the same which was attached to my GWT widget.
Not able to code it.
I've made the particular widget. Server side processing which includes raising JIRA request is remaining.
Please help.
Thanks
If you need to upload an attachment to a JIRA issue I would recommend you to use the JIRA built-in REST API.
See information on the operation of attachment POST here: https://developer.atlassian.com/static/rest/jira/4.4.1.html#id149632
And general information on REST implementation here:
https://developer.atlassian.com/display/JIRADEV/JIRA+REST+APIs
So basically the process would be as follows: You initiate upload from client side to your server, your server validates the file and then uploads file to JIRA via the REST API.