[
https://issues.apache.org/jira/browse/DIRSERVER-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016708#comment-17016708
]
Brian Burch commented on DIRSERVER-2298:
----------------------------------------
PosixAccount schema:-
Before: the objectClass m-oid 1.3.6.1.1.1.2.0 posixAccount is defined as
structural, metaTop, BUT it does NOT have MAY or MUST entries for uidNumber or
gidNumber.
resolution (must be an atomic update and the server must be restarted
afterwards):
dn: m-oid=1.3.6.1.1.1.2.0,ou=objectClasses,cn=nis,ou=schema
changetype: modify
add: m-must
m-must: uidNumber
-
add: m-must
m-must: gidNumber
-
add: m-must
m-must: homeDirectory
-
add: m-may
m-may: userPassword
-
add: m-may
m-may: loginShell
-
add: m-may
m-may: gecos
-
add: m-may
m-may: description
PosixGroup schema:-
Before: the objectClass m-oid 1.3.6.1.1.1.2.2 posixGroup is defined as
structural, metaTop, BUT it does NOT have MAY or MUST entries for gidNumber or
memberUid.
resolution (must be an atomic update and the server must be restarted
afterwards):
dn: m-oid=1.3.6.1.1.1.2.2,ou=objectClasses,cn=nis,ou=schema
changetype: modify
add: m-must
m-must: gidNumber
-
add: m-may
m-may: memberUid
> AM25 nis schema objectClasses missing must/attributes
> -----------------------------------------------------
>
> Key: DIRSERVER-2298
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2298
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: config
> Affects Versions: 2.0.0.AM25
> Environment: linux command line ldap tools, but also apacheds studio.
> Reporter: Brian Burch
> Priority: Minor
>
> The nis schema with M23 was 100% compatible with the openldap and rfc2307
> definitions of posixAccount and posixGroup. Apparently, these have not
> changed for at least a decade.
> After a clean install from git source and creating a new user partition, the
> schema has changed significantly. ( n.b. The schema can be enabled in the
> usual manner)>
> # It is impossible to create a new posixUser, posixGroup, or even assign
> these objectclasses to and existing user or group.
> # ldif files which successfully modified the schema with M23 no longer work
> with AM25 because the dn's of these two objectclass schema entries have
> changed!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
