How to Authorize PING ID token from client as Bearer token with IFS

Hi ​@InfSurajM 

Here you can find how the bearer token flow in IFS Cloud.

User Authentication - Technical Documentation For IFS Cloud

/Damith

Hi ​@dsj ,

Thanks for responding.I have already gone through the section in the link.However, in my case, client access token url is of PINGID not IFSCloud. So they are recieving the bearer token from PINGID. What we can share with PINGID/client in order of that incoming bearer token from PINGID gets validated in IFS.

Regards,

Suraj Mohan

Hi ​@InfSurajM 

Has the IFS configured to use PingID as external Identity Provider?

Hi ​@dsj ,

Yes, PINGID is configured in IFS for SSO login, which is working fine. But for Integrations, client is using system to system integration , that’s why they will send the bearer token generated in PINGID.

Regards,

Suraj

Hi ​@InfSurajM 

According to my experience, only the bearer tokens obtained through Authorization Code Flow (rendering a browser and login with a 3rd pard IDP) is supported with IFS Cloud. Below note from the documentation confirms the same.

If the PingID application can be setup to obtain a token using ROPC using a username which is in IFS,  then you might be able to use that token for IFS. I have not tried that and can’t say if it works for sure, and enabling ROPC is a security risk, so consider that as well.

Hope it helps!

Damith

dsj wrote:

Hi ​@InfSurajM 

 

According to my experience, only the bearer tokens obtained through Authorization Code Flow (rendering a browser and login with a 3rd pard IDP) is supported with IFS Cloud. Below note from the documentation confirms the same.

 

If the PingID application can be setup to obtain a token using ROPC using a username which is in IFS,  then you might be able to use that token for IFS. I have not tried that and can’t say if it works for sure, and enabling ROPC is a security risk, so consider that as well.

 

Hope it helps!

Damith

I take back my suggestion of using ROPC. According to the note, it’s not supported.