Authenticating users through Azure AD on IFS10, with the user's Directory ID synced from LDAP as their UserPrincipalName, fails with an unhandled 'object reference not set to an instance of an object'-style error. What actually causes this specific error?

All FAQ questions / Security and access

Answer

Check the platform type declared for the Enterprise Explorer client's Redirect URI in the Azure AD app registration — if it's declared as a 'Web' platform type, that's the wrong type and causes exactly this kind of authentication failure. It needs to be declared as a 'Mobile and Desktop Applications' platform type, what Azure AD documentation also refers to as a 'Public Client', instead, since Enterprise Explorer authenticates as a public/native client rather than a confidential web application — IFS's own documentation on this isn't entirely clear about which specific platform type is required, which is why this is easy to get wrong on first setup.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Security and access questions