Unable to sign in after integrating Okta with Azure Web App

Question

Unable to sign in after integrating Okta with Azure Web App. User created on azure is different while the okta developer account created with different user which does not have any privilege in azure . Does it create any problem while authenticating ?
After configuring the openID connect in web app using okta ,my web app URL is redirecting to okta login page but when i am putting the okta credentials it says "Unable to sign in" .
However I am able to login to Okta login page (developer account ).

Answer 1

Hi @Pooja-5119 ,
welcome to the Microsoft Q&A Platform!
"Unable to sign in" issue after integrating Okta with your Azure Web App.

Check Client Credentials and Redirect URI:

• Ensure that the Client ID and Client Secret in Azure match those configured in your Okta application.
• Verify that the redirect URI specified in Okta matches exactly with the one configured in your Azure app. Even small mismatches can lead to authentication errors.

User Permissions and Role Assignment:

• The user account in Okta should ideally have the necessary permissions for the Azure Web App. Assign appropriate roles to the Okta user account, especially if this account differs from the main user account in Azure. Misalignment in roles and permissions can prevent successful authentication.

User Attribute Mapping:

• Confirm that user attributes (such as email or username) are consistently mapped between Okta and Azure. You can configure this in the Okta dashboard by checking the claims mappings under the OpenID Connect settings. Ensure that attributes like email and preferred_username align between both services to avoid sign-in issues.

Check for Session Conflicts:

• Clear your browser cookies and cache to remove any session conflicts. Okta’s session duration or cookie policies may also need to be aligned with Azure’s session management settings to maintain a smooth sign-in flow.

Enable Logging:

• In Okta, review the System Log for specific error messages. Azure also offers diagnostic logging which can capture OpenID Connect issues. These logs can provide more insight into the failure point and help pinpoint configuration issues.

you can refer :
Okta OIDC setup or Microsoft’s guidance on OpenID Connect with third-party identity providers.
If the answer is helpful, please click "Accept Answer" and kindly upvote it.