-
Notifications
You must be signed in to change notification settings - Fork 7
Description
Great tool.
I used the script to create custom attributes for groups and another custom attribute for users. This worked fine. However, when I set a value of each attribute for a specific group or user, the script reports errors that such attribute is not part of the schema. However, it also reports that the value was set correctly, and when I look in the lldap UI, I can indeed see that the attributes were set correctly. I believe these errors about not being in the schema should not be reported. Perhaps the script needs to reload the group or user schema after it has been changed with new attributes?
Here are the error messages that I see when adding a group attribute and setting a value to it for a group
user:/#lldap-cli schema attribute group add gidNumber integer -v -e
added in schema new group attribute: gidNumber
user:/#lldap-cli group update set lldap_admin gidNumber 2001
ERROR: Attribute gidNumber is not part of group schema.
ERROR: Attribute gidNumber is not part of group schema.
Attribute set for group: lldap_admin, attribute: gidNumber, value: 2001
These error messages also appears in the logs for user attributes.
user:/#lldap-cli schema attribute user add krbPrincipalName string -v -e
Added in schema new user attribute: krbPrincipalName
user:/#lldap-cli user update set admin krbPrincipalName admin@example.com
ERROR: Attribute krbPrincipalName is not part of user schema.
ERROR: Attribute krbPrincipalName is not part of user schema.
Attribute set for user: admin, attribute: krbPrincipalName, value: admin@example.com
In both cases, the lldap UI shows the new attributes and the values set correctly, but the lldap-cli script reports an error.