Hello all, looking for a little help with an odd situation here. VPN units are MAG6611s running 7.4R9.3. I have a working realm that successfully authenticates off our AD domain controllers (auth server type is Active Directory, not LDAP). Nothing fancy. Couple of different roles behind it, role mapping rules are based on group membership. "Enable Group Search with LDAP" is not checked in the auth server setup, so my understanding is that means the MAG is using native AD methods to determine what groups users are in. OK, now the boss wants to enable two-factor authentication. I've done this before by creating a certificate auth server, having it generate the username from one of the fields in the cert, then configure the realm to use the certificate server first and the AD or LDAP server as secondary. Usually works fine. The issue here is that the users who access this realm are outside contractors, not employees of my company. So they get a login account in our AD, but they don't get a user certificate from us. They have user certificates from their employer. I have imported the necessary CA certs to be able to validate their user certs, no issue there. If I configure the certificate auth server to set their username to their email address like I usually do, it gets set to something like
[email protected] Then when the MAG goes to do the secondary authentication to my AD server with that, it fails. My Windows guy is telling me it's because the domains don't match, i.e. ours look like
[email protected] We tried changing the email address field in the user's AD login properties to
[email protected] but that still did not work, the AD authentication still fails. Any suggestions on how to make this work? I'm thinking I probably have to eliminate the certificate server auth and go back to just the AD auth, and then do something in the certificate restrictions screen to try to correlate something in their certs to something in my AD, but haven't figured out how to make that fly yet... Thanks, Chuck
... View more