I have faced the following scenario:
Customer uses IBM Domino Lotus ldap as additional ldap (some applications are authorizing from it), so I am going to create account collector.
The accounts' CN attribute is not collected
mail=<account mail address>
displayname=<account's lotus style fqdn, like Zoltan Izsak/Engineering/IT/RSA/HU>
mailaddress=<o365 account mailbox address>
department=<some department id>
givenname=<givenname, like Zoltan>
sn=<last name, like Izsak>
uid=<account id, which is concatenated first name and last name, like zoltanizsak>
I would like to collect CN for obvious reasons but I can only collect cn. Even if not collecting cn, CN is not collected, like it was not existing. The collector data source type is ldap. I have tried OpenLDAP, Other and OID as well. I tried to collect into several Aveksa attributes. None of the combinations could collect CN.
The same ldap contains groups as well. An example:
member=<member 1 fqdn>
member=<member 2 fqdn>
The account collector was not able to collect any groups. I tried to filter on objectclass=dominoGroup and objectclass=groupOfNames but both returned 0 groups. Base DN is near to the ldap root and I am searching in the subtree as well.
Any idea what is the problem?
- Community Thread
- Data Collection
- Forum Thread
- Identity G&L
- Identity Governance & Lifecycle
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL