[
https://issues.apache.org/jira/browse/DIRSERVER-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071442#comment-17071442
]
Emmanuel Lécharny commented on DIRSERVER-2298:
----------------------------------------------
So I tried something different :
- starting the server with nis disabled (the standard)
- enabled nis
- checked the posixAccount ObjectClass (not present...)
- restarted the server
- checked the posixAccount ObjectClass (now present and proper)
Here are the logs :
{noformat}
_ _ ____ ____
/ \ _ __ ___ ___| |__ ___| _ \/ ___|
/ _ \ | '_ \ / _` |/ __| '_ \ / _ \ | | \___ \
/ ___ \| |_) | (_| | (__| | | | __/ |_| |___) |
/_/ \_\ .__/ \__,_|\___|_| |_|\___|____/|____/
|_|
Before nis anabling
Entry
dn[n]: cn=nis,ou=schema
objectclass: metaSchema
objectclass: top
m-dependencies: system
m-dependencies: core
m-dependencies: cosine
cn: nis
m-disabled: TRUE
objectclass: metaSchema
objectclass: top
Entry
dn[n]: ou=objectClasses,cn=nis,ou=schema
objectclass: organizationalUnit
objectclass: top
ou: objectclasses
objectclass: organizationalUnit
objectclass: top
null
nis enabling
after nis anabling
Entry
dn[n]: cn=nis,ou=schema
objectclass: metaSchema
objectclass: top
m-dependencies: system
m-dependencies: core
m-dependencies: cosine
cn: nis
m-disabled: FALSE
objectclass: metaSchema
objectclass: top
Entry
dn[n]: ou=objectClasses,cn=nis,ou=schema
objectclass: organizationalUnit
objectclass: top
ou: objectclasses
objectclass: organizationalUnit
objectclass: top
posixAccount : null
_ _ ____ ____
/ \ _ __ ___ ___| |__ ___| _ \/ ___|
/ _ \ | '_ \ / _` |/ __| '_ \ / _ \ | | \___ \
/ ___ \| |_) | (_| | (__| | | | __/ |_| |___) |
/_/ \_\ .__/ \__,_|\___|_| |_|\___|____/|____/
|_|
Before nis anabling
Entry
dn[n]: cn=nis,ou=schema
objectclass: metaSchema
objectclass: top
m-dependencies: system
m-dependencies: core
m-dependencies: cosine
cn: nis
m-disabled: FALSE
objectclass: metaSchema
objectclass: top
Entry
dn[n]: ou=objectClasses,cn=nis,ou=schema
objectclass: organizationalUnit
objectclass: top
ou: objectclasses
objectclass: organizationalUnit
objectclass: top
posixAccount : Entry
dn[n]: m-oid=1.3.6.1.1.1.2.0,ou=objectClasses,cn=nis,ou=schema
objectclass: metaObjectClass
objectclass: metaTop
objectclass: top
m-may: userPassword
m-may: loginShell
m-may: gecos
m-may: description
m-typeobjectclass: AUXILIARY
m-supobjectclass: top
m-must: cn
m-must: uid
m-must: uidNumber
m-must: gidNumber
m-must: homeDirectory
m-description: Abstraction of an account with POSIX attributes
m-obsolete: FALSE
m-oid: 1.3.6.1.1.1.2.0
objectclass: metaObjectClass
objectclass: metaTop
objectclass: top
m-name: posixAccount
{noformat}
So first notice that the {{posixAccount}} objectClass is visible and complete.
What is important here is that the server was restarted, which led to the
{{nis}} schema to have been loaded properly because it was then enabled.
That means enabling a schema live is not working. This should be fixed.
> 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]
