Dynamics Community Forum Thread Details

Loggin into to Dynamics 365 from OneLogin

Until recently (with no alterations made to OneLogin aor Dynamics that I know of) we started receiving the following error when trying to access out Dynamics 365 Hub from our OneLogin SSO page:

Error

An error has occurred.

Try this action again. If the problem continues, check the Microsoft Dynamics 365 Community for solutions or contact your organization's Microsoft Dynamics 365 Administrator. Finally, you can contact Microsoft Support.

Timestamp: 8/15/2025 8:58:03 PM UTC
Service Request Id: 53a9e369-172a-453a-810d-d6303f59b6d0

Tenant Id: 8105bc5d-cc07-4843-b37d-81d7e1187c0b
Url: https://prpllc.crm.dynamics.com
Organization Id: 31df3532-0e4d-ee11-94d0-6045bd003903
Unique name: unq31df35320e4dee1194d06045bd003
Security Group: Not set

When you click the 'Try Again' button, the SSO process goes through and take you to the Dynamics 365 site.

When i presented the issue to OneLogin support and sent them a SAML TRacer Log as they requested, they informed me that they found out the error is related to 'validator; but not sure how to resolve it with the Dyanmics applicaiton and I should reach out to MS support.

I am also attaching the SAML trace log in JSON format

Categories:

Dynamics 365 general

Hi there,

Thanks for sharing the details. Based on your description and the SAML trace log feedback from OneLogin support, it seems the issue is related to SAML token validation during the SSO process between OneLogin and Dynamics 365.

Here are a few steps you can try:

Check SAML Configuration
- Ensure that the SAML assertion includes all required claims (e.g., NameID, email, userPrincipalName).
- Verify that the audience URI and recipient URL match the expected values in Dynamics 365.
Dynamics 365 Setup
- Confirm that the Azure AD tenant is correctly linked to your Dynamics 365 environment.
- Check if the user exists in Dynamics 365 and is assigned the correct security roles.
OneLogin Settings
- In OneLogin, verify that the application connector for Dynamics 365 is up to date.
- Make sure the X.509 certificate used for signing is valid and matches what Dynamics expects.
Microsoft Support
- Since OneLogin identified a validator issue, and the error persists after SSO, it’s best to open a support ticket with Microsoft and include the SAML trace log and Service Request ID for deeper investigation.