Managing external identities to enable secure access for partners, customers, and other non-employees
Azure Entra External ID + OIDC Federation - Local and Federated Identities Issue
Saravana Kumar Palanisamy
30
Reputation points
I’m integrating Entra External ID (CIAM) with an external OIDC identity provider (Azure AD B2C). I’m creating users in the EEID tenant using Microsoft Graph, and giving them both local and federated identities with Password profile
Here’s the identity fetched after creating:
"identities": [
{
"signInType": "federated",
"issuer": "https://demodigitalb2c.b2clogin.com/*******-7659-4181-8671-7e4c934bfdcf/v2.0/</*******--a3ec-4fa7-a471-d4eb8006dedb>",
"issuerAssignedId": "8180e51e-aa7b-403d-9bbc-a27b8f728562"
},
{
"signInType": "emailAddress",
"issuer": "demodigitalciamuat.onmicrosoft.com",
"issuerAssignedId": "******@email.ghostinspector.com"
},
{
"signInType": "userPrincipalName",
"issuer": "demodigitalciamuat.onmicrosoft.com",
"issuerAssignedId": "925bfbdc-c51d-444f-886c-
removed PII
}
],
The Issues faced are
- When I go to the login page and enter the email address, I get: “There was an issue looking up your account. Tap Next to try again.”
1.If I click the Federated login button, it redirects to the external IdP and logs in successfully.
- If I click the Federated login button, it redirects to the external IdP and logs in successfully.
- But after logging out and trying again, the login page shows: AADSTS50000: There was an error issuing a token or an issue with our sign-in service.
Can you please help on this.
Microsoft Security | Microsoft Entra | Microsoft Entra External ID
Microsoft Security | Microsoft Entra | Microsoft Entra External ID
Sign in to answer