We currently have three Kerberos servers running 1.9.4 using the LDAP
backend and are planning to upgrade to 1.13. Historically we have always
upgraded servers one at a time, slaves first, then the master, and done the
upgrade in place with the temporary existence of different versions.
This is th
>From a pure LDAP perspective; You should be able to update schema in an
unobtrusive way as long as none of the attributes are "mandatory" for the
objectClass. If upon examination of the schema any of those new attributes
are mandatory as opposed to optional, then you have a requirement to update
I am going to need to make the exact same update at some point, so a report
back on how it went would be great!
Thanks,
Chris
On Dec 3, 2014 2:28 PM, "Paul B. Henson" wrote:
> We currently have three Kerberos servers running 1.9.4 using the LDAP
> backend and are planning to upgrade to 1.13. Hi
> From: Todd Grayson
> Sent: Wednesday, December 03, 2014 3:07 PM
>
> From a pure LDAP perspective; You should be able to update schema in an
> unobtrusive way as long as none of the attributes are "mandatory" for the
> objectClass.
All of the new attributes are optional, so no problem there.
>
> From: Chris Hecker
> Sent: Wednesday, December 03, 2014 4:21 PM
>
> I am going to need to make the exact same update at some point, so a
> report back on how it went would be great!
Heh, no chance I could talk you into going first ;)?
We will probably be working on this in January, I'll hang on
