SAML2.0 Azure AD and DeepLinks

0
Hi,   Recently upgraded an app from Mendix 8 to 9 and have started to use Azure AD and the SAML2 module.  Everything works fine with the SSO if my users go to the 'home' page but when they try and use a DeepLink, the get a 404 Nginx error, and I've noticed that in the address bar in the browser, it looks like the urls are malformed and duplicated.   so users are going to htts://app.domain.com/link/SSRS   and in the address bar on the 404 nginx error it says https://app.mendixcloud.com/http://app.mendixcloud.com:80/link/SSRS   If I then paste the link back in again, it works and logs in and takes me to the deeplink.   I cannot figure out why this is happening.  I;ve looked at all of the constants and set them up how they should be.  Do I need to add something to the SSO configuration in Azure?  I already have the Urls configured for Identity (app.domain.com) and Reply Url (app.domain.com/SSO).   Any ideas?
asked
2 answers
1

Hello Ben,

Check if the DeepLink microflow is properly set up and configured.

Have you created Deeplink microflow in the NV_Home page and checking whether it’s deeplink or not?

You can add debugger and check the value are correct.

answered
1

Hi Ben, this usually happens when SAML20.ApplicationRootUrl constant is misconfigured. Make sure it's set exactly "https://app.domain.com" (no trailing slash or port). A malformed value here can cause the redirect URL to get duplicated, leading to a 404 from NGINX.

 

Also:

  • Ensure you're using the latest DeepLink module.

  • Check that DeepLinkHome is correctly set up.

  • Optionally, try  setting SAML20.UseHttpPostBindingForAuthnRequest = true if issues persist.

Once ApplicationRootUrl is correct, deep links should redirect properly after SSO.

 

Reminder:

After changing the constant Restart the app to apply changes. Re-test using an incognito/private window to avoid caching issues.

 

I hope this one helps you! :)

answered