03-31-2023 08:15 AM
We have historically used Active Directory SAMAccountName to leverage SSO into Perceptive full client. If we wanted to change our User IDs in Perceptive to be in the UPN/Email Address format, could we leverage SSO against Active Directory UPN instead? We've tried it, but the client refuses to do SSO and always prompts for Active Directory password (which works when typed in). Thank you!
03-31-2023 09:07 AM
Thanks for the clarification. The client auto-logon method uses two things to provide this capability. The first is that there is a defined list of domains in the server configuration that must match a domain for the clients accessing the system. The second piece that is needed is the Windows logon username must be a valid Content user. When a user attempts to login with a connection profile that is configured for auto-login the client will pass the username of the windows user and the domain to the server, if the domain is in the list the server will then check the username against the Content user store. If both match the session will be established. We do not provide a way to map the username to use to any other value other than Windows logon username unfortunately.
03-31-2023 11:42 AM
03-31-2023 12:05 PM
USERDOMAIN=PVI
USERDOMAIN_ROAMINGPROFILE=PVI
USERNAME=bcrespino
Those are the two values that are used for this configuration to work.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.