It would be great if Jet would offer support to login with the UPN suffixes as configured in Active Directory. We work in multi tenant environment where each OU has their own UPN suffixes to represent the actual email addresses of the user.

Those UPN suffixes are therefore different than the actual domain where the servers are domain joined.

When we login in different other applications, the UPN and password are being validated in AD and authenticated if correct. This however doesn’t work in Jet, Jet always tries to match a different UPN suffix with a different domain, which of course does not exist and thus the authentication fails.

Example;

Users login with their UPN

UPN: Firstname.lastname@customerdomain.com

The UPN suffix doesn’t match the domain “Contoso.com” where Jet has been installed, Jet fails to authenticate those users.

If we change the user their UPN to firstname.lastname@contoso.com it works.

Login with samaccount name is also possible but this is a format that the user doesn’t and shouldn’t now. (contoso\firstname.lastname_customercode)

For multiple reasons we cannot use firstname.lastname@contoso.com, one of them is duplicate UPN’s which is of course not supported in AD.

It would be great if there would be a setting to let Jet know to only authenticate against the local domain controllers, or an option where you can specify different UPN suffixes so Jet knows that those are local domain users.