
2g3mw (2g3mw) asked a question.
Hi,
We want a solution where :
1)App 1 calls Okta to get an Oauth token, passing a client id/secret.
2)Okta calls Pingfederate and passes on the credentials.
3)Pingfed authenticates and responds to Okta.
4) Okta generates a token upon successful authentication and returns to App1.
5)App1 uses that token to call a webservice in App2.
Is this possible? Could you please guide me to some pointers/documentations etc I can read up on this integration pattern?
The reason we want this is because we want Pingfed to control the clientid-secret onboarding/offboarding, but "App2" in example above uses Okta as their IDP.

Hello @2g3mw (2g3mw) Thank you for posting on our Community page!
You could add Ping as an IDP in Okta, this way Ping will be the Profile master in for the users in Okta. Then you can configure the App2 in Okta and Okta will be the IDP for that.
To configure the Ping as an IDP in Okta please see our doc below, for SAML and OIDC:
https://help.okta.com/en-us/content/topics/security/idp-add-saml.htm
https://developer.okta.com/docs/guides/add-an-external-idp/openidconnect/main/
After this is done App1 calls Okta, Okta then sends the user to Ping for authentication the the user is send back to App1 authenticated, from there the App1 can login the user further on to App2.
Additionally if you need further assistance we recommend to leverage the Okta Developer forums for this type of questions and take advantage of their expertise.
https://devforum.okta.com/
Thank you for reaching out to our Community and have a great day!
--
Join the discussion for the Ask Me Anything online event on May 23, 2024 with Okta Tactical Edge Product Experts