Share via

unable to view external oidc idp in an userflow

Rajan Ramasamy 0 Reputation points
2025-12-10T02:57:30.8833333+00:00

Unable to view an external oidc idp configured for federation.

Microsoft Security | Microsoft Entra | Microsoft Entra External ID
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sridevi Machavarapu 8,850 Reputation points Microsoft External Staff Moderator
    2025-12-10T03:14:40.82+00:00

    Hey Rajan Ramasamy! It sounds like you’re having trouble viewing an external OIDC identity provider that you’ve set up for your user flow. Here are some steps you can follow to troubleshoot and ensure that it's properly configured:

    1. Check User Flow Configuration: Make sure that you have added the external OIDC identity provider to the correct user flow. To do this:
      • Go to Microsoft Entra ID > External Identities > User flows.
      • Select the user flow that you want to check.
      • Under Settings, choose Identity providers and ensure your OIDC identity provider is listed under Other Identity Providers.
    2. Verify Configuration Parameters: Ensure that your OpenID Connect settings include the correct:
      • Well-known endpoint (metadata URI): This should return the necessary configuration for your identity provider.
      • Redirect URIs should be populated correctly (check against your application configuration).
    3. Registered Application: Ensure that your application is properly registered in the external tenant and all required permissions are assigned (e.g., Directory.ReadAll, User.Read, etc.).
    4. Client Secret: If you are using a client secret, verify that it hasn’t expired. If needed, generate a new one in your Microsoft Entra application and replace the existing one in your configuration.
    5. Testing the Setup: After you've confirmed all configurations, attempt to sign in again. Sometimes, it may be necessary to clear browser cache or try signing in from an incognito window.
    6. Permissions: Ensure that admin consent has been granted for all necessary API permissions.

    If you continue to have issues after checking these points, please provide more details:

    • What exact steps did you follow when setting up the OIDC provider?
    • Are you seeing any error messages, or is the provider simply not appearing?
    • Can you confirm that the OIDC identity provider is functioning independently outside of Azure (e.g., through a direct test)?

    Hope this helps, and looking forward to your reply with more details!

    Relevant Documentation:

    Note: This content was drafted with the help of an AI system.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.