We were able to find some information on how to extract the attributes and use traffic policies however not very sure how to use those. Top Results For Epic Remote Access Nychhc Updated. LDAP policies are configured to use samaccountname currently. org using your username/passwords and Symantec VIP access application. Is there a way we can extract mail attribute for the users during the first authentication which is LDAP and once it is successful, NetScaler should send the mail attribute to Azure using NPS as RADIUS only. Register the credential shown in the VIP Access app Open the VIP Access app you just installed. To access the Self Service Portal, enter your user name and password, and click Sign In. The 2FA works well if the samaccountname matches the mail attribute of the user and it matches the one in azure as well. Welcome to the Symantec® VIP Self Service Portal. Since NPS recieved samaccountname from Netscaler and not mail attribute, Azure errors out stating the user name does not exist or not found. User when provide samaccountname as primary ldap authentication, Netscaler verifies the same and pass on the same user details to NPS server which in turn communicates to Azure. the samaccountname does not match to the mail attribute synced to Azure. Access Agent for Windows from the browser-based UI login page. The scenario we have currently is for the users who have samaccountname as "test" and mail atribute synced to azure as test.n i.e. Symantec Privileged Access Manager - 4.1.2. This resolves my half of the problem.I tested 2nd factor using NPS and it is working fine only for the user whose samaccountname matches the mail attribute which is synced to Azure AD. Symantec VIP Access functions like many two-factor apps including Google Authenticator, KeyPass, and Duo Security.
0 Comments
Leave a Reply. |