Resolution
goal
When using Active Directory as an external authentication source VigilEnt Security Manager needs to map to SamAccountName and not the CN.
fact
VigilEnt Security Manager 4.0
cause
This is a known issue within the external authentication feature of VigilEnt Security Manager (VSM). Instead of the login name within VSM mapping to the SamAccountName in Active Directory, it maps to the CN name.
fix
This issue is resolved in VigilEnt Security Manager 4.1 available for download from https://www.netiq.com/support/default.asp.
When using Active Directory as an external authentication source VigilEnt Security Manager needs to map to SamAccountName and not the CN.
fact
VigilEnt Security Manager 4.0
cause
This is a known issue within the external authentication feature of VigilEnt Security Manager (VSM). Instead of the login name within VSM mapping to the SamAccountName in Active Directory, it maps to the CN name.
fix
This issue is resolved in VigilEnt Security Manager 4.1 available for download from https://www.netiq.com/support/default.asp.
Additional Information
Formerly known as NETIQKB29263