asked on September 20, 2022
User is just setting up LF and is unable to log into the Web client using their UPN, they are forced to use their FQDN (username@company.local). All of their users are setup with first.last@company.com for UPN and they would like to sign in this way. We've created a new identity provider in LFDS with company.com, and that allows users that have the same SAMAccount name as UPN to login, when standard users try they are only able to login using their SAML and not UPN.
How does this need configured to allow them to sign in using their UPN account?
0
0