Hey Stefan,
Ah that concept escaped me..at the moment this looks like
# gaPlayer
objectclass ( 1.3.6.1.4.1.99999.1.2.1
NAME 'gaPlayer'
DESC 'LDAP representation of a player'
SUP inetOrgPerson
STRUCTURAL
MUST ( cn $ gaPlayerGuid $ gaPartnerRef $ gaPartnerWebKey $
gaSessionWebKey $ gaPlayerTokenId $ gaPlayerId $ gaComment $
gaBaseCurrency )
)
one point I didn't mention is that this schema is coming straight from
openldap..so you're suggesting I change Structural to Auxiliary? However
I am using other bits and pieces from other
schemas, like "mail" and "sn" and those don't seem to blow up..
Thanks,
Yiannis.
Stefan Seelmann wrote:
Right, the 'c' attribute is declared in the core schema. However you
need to add it (and also the other existing attributes) to your
gaPlayer objectClass, either as m-must or m-may.
However I would recommend another approach: Define your gaPlayer
objectClass as 'auxiliary' with your gaXYZ attributes. Then use an
existing object class (e.g inetOrgPerson) as structural object class
and gaPlayer as additional object class for your users:
dn: cn=imavroukakis,ou=Player,dc=gameaccount,dc=com
objectClass: top
objectClass: inetOrgPerson
objectClass: gaPlayer
...
Kind Regards,
Stefan
