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. These tokens will only work with Symantec VIP Access. Offer your users the ultimate in convenience and security with Symantec VIP Access. LDAP policies are configured to use samaccountname currently. any software Secure, sturdy, and long-life hardware design Easy to use Portable key chain design. 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. Symantec VIP Quick Start Guide Helping your users Configuration Summary VIP Self-Service Portal: Internal only Enabling the VIP Self Service Portal for internal access only simply requires enabling the capability on one VIP Enterprise Gateway within the environment. Symantec VIP is an identity management software that helps organizations to manage and protect their online identities. The 2FA works well if the samaccountname matches the mail attribute of the user and it matches the one in azure as well. To download onto a mobile device, download the VIP Access app from the Google Play Store (Android) or the Apple App Store (iOS/iPadOS) To purchase a hard token, visit the Symantec store on Amazon. Since NPS recieved samaccountname from Netscaler and not mail attribute, Azure errors out stating the user name does not exist or not found. Where can I download a VIP Credential ID or token To download onto a computer, visit the Symantec VIP download page. 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. For us, VIP Access Manager is a very easy to use platform and it facilitates us up to 5 simultaneous separate devices per user and a backup temporary security. 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |