Skip to main content

Hello All,

I'm looking for some guidance on token authentication to/from PSO from a third party application.

Referring to the SchedulingSchema.pdf I know that the load file needs to be constructed to contain a <Broadcast> block with a <broadcast_type_id> of 'REST'.

The load file will also need <Broadcast_Parameters> containing 'auth_token_url', 'username' and 'password'.  From my understanding, when these entries are in the load file, when the load file is received and processed the Broadcast Manager will use the mentioned credentials to authenticate using client credentials flow.

This is where I am looking for further clarification.

Does PSO store the received token in the PSO database?

If PSO does store the token in the PSO database, do the subsequent DSE Broadcasts contain the token in each broadcast message?  If the token is NOT contained in the DSE Broadcast messages can PSO be configured to add the token to ALL DSE Broadcasts?

Any and all information and assistance will be greatly appreciated!

Hi @Paul Drennan ,

We were able to connect with PSO via the PSO RESTFul Gateway using Postman and a third party app sometimes back. While this might not be the most ideal solution for your question, I wanted to share how we did it. Keep in mind, I'm not a PSO expert! 🙂 To integrate with a third-party application using the PSO RESTful Gateway, you'll need to enable the EnableSwaggerUi parameter on the PSO side. This will provide interactive Swagger documentation at https://yourHostName/IFSSchedulingRESTfulGateway/swagger/ui/index.html, outlining the available HTTP methods.

To authenticate with the RESTful Gateway, you'll need to obtain a session token key using your PSO account ID, integration username, and integration password. The SessionRetentionSeconds ADM parameter determines the token's expiration time AFAIK.

Once you have the token, you can interact with PSO through the RESTful Gateway by including the token (apiKey) in the HTTP header of your requests.

I merely explained how the third-party app can communicate with the PSO, but I'm not sure how to reverse the process and have the PSO interact with the third-party app in the same way as you have asked here.

Hi,

Thanks for reaching out.

I’ve been able to successfully authenticate with the PSO token.

What the customer is trying to do is authenticate with OAUTH2 so that any broadcast messages sent from PSO contain the OAUTH token.

I can construct the OAUTH entries in the PSO load file, I just need to understand how PSO stores the OAUTH token and if all of the DSE Broadcasts can contain the OAUTH token.

@Paul Drennan did you see this thread:
 


Maybe the guy can help you out?

Best regards
Roman​​​​

Thanks Roman,

This covers everything the customer needs.

Much appreciated.

 

Kindest regards,

Paul

Reply


Terms & ConditionsCookie settings