Thanks to both of you. It is hard to know when changing something is acceptable and when there is a deeper problem.On to the next issue.-Mont
--
Fedora-directory-users mailing list
Fedora-directory-users@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users
* mailRoutingAddress
* mailHost
* inetLocalMailRecipient
* kerberosSecurityObject
* krbName
Is not having these in my schema common/normal?
I'm sure there's plenty of directories out there that don't maintain
these attributes on account objects.
If all you want to do is i
On Mon, 2006-03-27 at 09:08 -0800, Mont Rothstein wrote:
> Thank you for your reply.
>
> I grabbed the migration scripts from http://www.padl.com/download/
> because I wanted to avoid installing openldap when all I needed was
> the scripts.
>
> Looking at the source the kerberosSecurityObject is
Thank you for your reply.I grabbed the migration scripts from http://www.padl.com/download/ because I wanted to avoid installing openldap when all I needed was the scripts.
Looking at the source the kerberosSecurityObject is inserted as long as there is a default realm, though the extended schema
On Fri, 2006-03-24 at 10:26 -0800, Mont Rothstein wrote:
> A suggestion was made that I should add the contents of my
> sambaAdmin.ldif file to this post. They are below.
>
> The kerberosSecurityObject isn't in my schema, so thus the error. But
> why did migrate_password.pl put that in my ldif?
A suggestion was made that I should add the contents of my sambaAdmin.ldif file to this post. They are below.The kerberosSecurityObject isn't in my schema, so thus the error. But why did migrate_password.pl put that in my ldif? Is there a config option somewhere that should be switched to disabl
