CODEWITHSUNDEEP
azure-ad-b2copenid-connectokta
colinwurtz
colinwurtz

Reputation: 723

Okta redirect URI when used as OpenID IDP provider in Azure AD B2C

I'm trying to set up Okta as an OpenID Connect provider in my Azure AD B2C tenant. Something is off with my configuration. It's throwing an error when I test the B2C user flow saying:

Error Code: invalid_request
Description: The 'redirect_uri' parameter must be a Login redirect URI in the client app

Here are the steps I followed

Okta

https://B2CTenantName.b2clogin.com/B2C tenant ID/oauth2/authresp https://colinwurtzb2c.b2clogin.com/eb178344-61bd-4822-95cf-7a251aaba527/oauth2/authresp

Azure

List item

Upvotes: 0

Views: 940

Answers (2)

colinwurtz
colinwurtz

Reputation: 723

In addition to being consistent with the link, I had to add a few scopes in the custom IDP screen and map email to User ID in the claims mapping section.

enter image description here

Upvotes: 0

wojtekdo
wojtekdo

Reputation: 414

I believe you need to be consistent which URL pattern / tenant identifier you use. If you set up Okta application with https://colinwurtzb2c.b2clogin.com/eb178344-61bd-4822-95cf-7a251aaba527/oauth2/authresp (using tenant Id) then you need to open your user flow also using tenant Id. Your screen shows the default Azure Portal option with tenant name, so the URL starts with https://colinwurtzb2c.b2clogin.com/colinwurtzb2c.onmicrosoft.com/(...). My guess is that in this case AAD B2C makes a request to Okta using https://colinwurtzb2c.b2clogin.com/colinwurtzb2c.onmicrosoft.com/oauth2/authresp which is different then the one you set up and hence the error. So, either set up Okta with the URL including tenant name or use tenant Id while running AAD B2C user flow.

Upvotes: 1

Related Questions