[
https://issues.apache.org/jira/browse/DIRSERVER-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114415#comment-17114415
]
Emmanuel Lécharny commented on DIRSERVER-2298:
----------------------------------------------
I can confirm that enabling the {{nis}} schema live works, but the problem is
that a schema aware connection will not be able to do a lookup on the
{{posixAccount}} ObjectClass because the connection schema manager does not
know about it... We should first reload the client schemaManager before
accessing the server's newly enabled schema...
> 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]
