We would like to populate the Other Name Attribute which I believe is an
extension of the CN with our Employee ID attribute. We want the users to be
able to use either credential (CN or Employee ID) for User Application
authentication. Some users may not know their real cn as it is being
automatically generated. Most systems are using the Employee ID as the CN
but we cannot do this at the main vault at user creation time because we may
not have an Employee ID (vendors) and may need to fire a custom driver to
generate the Employee ID for that user. The Employee ID is always a
Character followed by 6 numbers so it would be easy to pick out in a policy.
What are the negatives of having a multi-value CN?