On Wed, Oct 25, 2006 at 08:22:42AM -0400, Edgecombe, Jason wrote:
What about making positions as owners?
people - positions - machines. People may have multiple
positions/jobs and the job is responsible for the machine.
Groups give you the same functionality without inventing something
Two things, One, I thought that there already was a Kerberos Security
Object Class for LDAP, it just so happens MIT Kerberos cannot use it.
Secondly, when are we going to see in smbldap-tools a patch to
allowsmbldap-useradd to add a Kerberos Principal when it adds a user?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Henry B. Hotz
Sent: Wednesday, October 25, 2006 12:30 AM
To: Nicolas Williams
Cc: [EMAIL PROTECTED]; kerberos@mit.edu
Subject: Re: LDAP Schema Design Suggestions?
On Oct 24, 2006, at 7:35 PM, Nicolas Williams
No, I'm not talking about using LDAP to store the back-end for a KDC.
I'm wondering if there are any thoughts or wisdom related to RFC 2307
(or successors) about how to store meta-information about Kerberos
principals. That RFC defines schema's for machines and things with
IP numbers. I
On Tue, Oct 24, 2006 at 06:19:04PM -0700, Henry B. Hotz wrote:
No, I'm not talking about using LDAP to store the back-end for a KDC.
I'm wondering if there are any thoughts or wisdom related to RFC 2307
(or successors) about how to store meta-information about Kerberos
principals. That
On Oct 24, 2006, at 7:35 PM, Nicolas Williams wrote:
On Tue, Oct 24, 2006 at 06:19:04PM -0700, Henry B. Hotz wrote:
No, I'm not talking about using LDAP to store the back-end for a KDC.
I'm wondering if there are any thoughts or wisdom related to RFC 2307
(or successors) about how to store
