I don't think it would be possible to troubleshoot this on the community without the full set of logs.
I recommend you open a case with RSA Support (How to contact RSA Support).
Hi Mostafa
Thanks for you response. We managed to resolve the issue. We had an username instead of an object class in our AFX configuration, thus upon trying to provision accounts to AD we get greeted by that error.
We changed the LDAP object calsses to create account from a username to the below.
I've seen in one on the documents here, they have AveksaAdmin as their object class, wouldnt that throw an error ?
Please help me understand.
Yes the LDAP object classes are LDAP-specific values necessary to be able to access the set of attributes needed while perform the actions (ref: https://ldap.com/object-classes/).
So yes you should not mess with these values unless you need to update extra attributes that are not provided by the existing set of classes.
Hi Mostafa
Thanks for you response. We managed to resolve the issue. We had an username instead of an object class in our AFX configuration, thus upon trying to provision accounts to AD we get greeted by that error.
We changed the LDAP object calsses to create account from a username to the below.
I've seen in one on the documents here, they have AveksaAdmin as their object class, wouldnt that throw an error ?
Please help me understand.