CODEWITHSUNDEEP
azure-ad-b2coktafederated-identityazure-ad-b2c-custom-policy
Marina Gurevich
Marina Gurevich

Reputation: 61

AD B2C integration with OKTA when OKTA is external IDP

We have a requirement to integrate ADB2C with Okta as an external Identity Provider. There are 3 use cases I see:

  1. Okta has users in the directory and those are users local to Okta.
  2. Okta has users imported from the on-prem Active Directory and authenticated with AD credentials via Okta.
  3. Okta has an Azure AD or other IDP configured as an external IDP (SAML or OIDC). To authenticate those users Okta /authorize url endpoint needs to be called and on each successful authentication an external IDP user becomes an JIT (just-in-time) Okta user, from what I've read in Okta docs.

I was able to set up B2C integration with Okta for #1 and #2 via B2C Custom policies. However, for the #3 I am wondering if it's even possible. And if yes than how. Because in this case Okta would be getting a token from an external IDP and then somehow forwarding that token to AD B2C and B2C would return it to the client. Has anyone had a similar experience/requirement?

Upvotes: 0

Views: 701

Answers (1)

Pruthvi Raj Nadimpalli
Pruthvi Raj Nadimpalli

Reputation: 1373

Okta will not forward the token from it's external IDP to Azure B2C instead it will generate it's own token and pass it to Azure B2C.

If you need the actual token from Okta's external IDP, you will need to use the following API: https://developer.okta.com/docs/reference/api/idps/#social-authentication-token-operation

Upvotes: 1

Related Questions