Hi!
It seems objectclass "pwdPolicy" (1.3.6.1.4.1.42.2.27.8.2.1) got attributetype "pwdMaxRecordedFailure" (1.3.6.1.4.1.42.2.27.8.1.30) added recently.
Shouldn't the OID of the objectclass change then? Anyway, how should I upüdate the schema using cn=config?
Regards, Ulrich P.S. You can find a similar question at serverfault.com
--On Monday, July 13, 2020 4:24 PM +0200 Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de wrote:
Hi!
It seems objectclass "pwdPolicy" (1.3.6.1.4.1.42.2.27.8.2.1) got attributetype "pwdMaxRecordedFailure" (1.3.6.1.4.1.42.2.27.8.1.30) added recently.
I personally don't consider a change that's nearly 5 years old to be recent, no.
Shouldn't the OID of the objectclass change then?
No, the OID of the parent objectClass should not be changed.
Anyway, how should I upüdate the schema using cn=config?
You could use ldapmodify. You could use slapcat/slapadd.
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Quanah Gibson-Mount quanah@symas.com schrieb am 14.07.2020 um 17:35 in
Nachricht <B87BA9840A4C9E9AF21E5764@[192.168.0.156]>:
--On Monday, July 13, 2020 4:24 PM +0200 Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de wrote:
Hi!
It seems objectclass "pwdPolicy" (1.3.6.1.4.1.42.2.27.8.2.1) got attributetype "pwdMaxRecordedFailure" (1.3.6.1.4.1.42.2.27.8.1.30) added recently.
I personally don't consider a change that's nearly 5 years old to be recent, no.
Depends on age ;-)
Shouldn't the OID of the objectclass change then?
No, the OID of the parent objectClass should not be changed.
Anyway, how should I upüdate the schema using cn=config?
You could use ldapmodify. You could use slapcat/slapadd.
So what you are saying is: Find out the diff yourself, write a corresponding LDIF file, and then apply it?
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
--On Wednesday, July 15, 2020 10:17 AM +0200 Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de wrote:
So what you are saying is: Find out the diff yourself, write a corresponding LDIF file, and then apply it?
If you go the ldapmodify route, that would be necessary. If you use slapcat/slapadd, no, you could strip out the old schema and import the updated ppolicy.ldif file.
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org
-
Quanah Gibson-Mount -
Ulrich Windl