On 11/26/18 8:35 PM, Alistair Cunningham wrote:
On 27/11/2018 12:32, Mark Reynolds wrote:
> On 11/26/18 7:44 PM, Alistair Cunningham wrote:
>> Thank you, I'll give that a go.
>> On a related topic, do you know why when I try to add a
>> simpleSecurityObject, I get a 'attribute "cn" not allowed'
>> $ cat 1234567890.ldif
>> dn: cn=1234567890,ou=2,dc=integrics,dc=com
>> objectClass: simpleSecurityObject
>> userPassword: abcdef
>> $ ldapadd -x -D "cn=Directory Manager" -w secret -f 1234567890.ldif
>> adding new entry "cn=1234567890,ou=2,dc=integrics,dc=com"
>> ldap_add: Object class violation (65)
>> additional info: attribute "cn" not allowed
>> I've tried with "uid=1234567890" instead, and it tells me that uid
>> is not allowed.
> You need an objectclass that allows CN or UID, simpleSecurityObject
> only allows the userpassword attribute
I see, thank you. In that case, what DN should I use instead of
"cn=1234567890,ou=2,dc=integrics,dc=com" for this
simpleSecurityObject? If no DN, how do I specify the
You should add an objectclass that allows CN (or UID), for example:
Technically you don't even need simpleSecurityObject, just "person"
alone will get you the entry that you need.