- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
08-15-2018 03:31 AM
When configuring edirectory as an Auth source, the client has replaced the LogonUserName field to be a CN, not UID - updating this field, I now receive ITATS701E, ITATS307E - there's nothing in the messaging and responses guide reflecting 307E - but the ITALOG says it's a parameter conflict. Directory Mapping for groups seems to work as expecting - searching for the vault groups by cn=Vault* lists only the groups relevant here, but when searching for users, even with "VaultUsers" specified in the mapping, all users are listed, not just those in the group - could this be the conflict - and if so, how do I resolve it?
08-15-2018 07:00 AM
so it turns out, after a few more tests, that the CN value was multivalued - which isn't currently supported by CyberArk - we had to change to an alternate value, which was just a single value duplication of the base CN for this customer - and we're now able to authenticate - nice 🙂
08-15-2018 07:00 AM
so it turns out, after a few more tests, that the CN value was multivalued - which isn't currently supported by CyberArk - we had to change to an alternate value, which was just a single value duplication of the base CN for this customer - and we're now able to authenticate - nice 🙂
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

