Ask Your Question

Keystone LDAP default structural class for users

asked 2013-10-02 12:33:00 -0500

asgreene gravatar image

Keystone allows one to specify the objectclass that represents users in LDAP, but is hard-coded to add 'person' as a structural class.

#TODO(termie): turn this into a data object and move logic to driver
class UserApi(common_ldap.EnabledEmuMixIn, common_ldap.BaseLdap):
    DEFAULT_OU = 'ou=Users'

This prevents the usage of custom object classes in an LDAP that do not inherit from person. Person brings attribute baggage along with it. Why is the person structural class hard-coded in here? Shouldn't it be either absent or configurable. If the LDAP class is being specified, let that be the object class and stipulate that it must be structural.

Am I missing something? Is there some rationale for this?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2016-06-28 16:29:40 -0500

That is just the default. The classes used are specified in the config:

user_objectclass = cfg.StrOpt( 'user_objectclass', default='inetOrgPerson', help=utils.fmt("""
LDAP objectclass for users. """))

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-10-02 12:33:00 -0500

Seen: 152 times

Last updated: Jun 28 '16