2005-01-11 17:04:58 +03:00
dn: @INDEXLIST
@IDXATTR: cn
2005-03-23 03:07:21 +03:00
@IDXATTR: flatname
2005-01-29 07:03:12 +03:00
@IDXATTR: realm
2005-01-11 17:04:58 +03:00
2005-03-23 03:07:21 +03:00
dn: @ATTRIBUTES
realm: CASE_INSENSITIVE
flatname: CASE_INSENSITIVE
sAMAccountName: CASE_INSENSITIVE
2005-08-03 11:25:36 +04:00
#Add modules to the list to activate them by default
#beware often order is important
dn: @MODULES
2005-10-12 11:57:39 +04:00
@LIST: operational
2005-08-03 11:25:36 +04:00
2005-01-11 17:04:58 +03:00
dn: CN=LSA Secrets
objectClass: top
objectClass: container
cn: LSA Secrets
2005-01-16 01:15:12 +03:00
dn: CN=Primary Domains
objectClass: top
objectClass: container
cn: Primary Domains
2005-03-19 11:11:49 +03:00
dn: flatname=${DOMAIN},CN=Primary Domains
2005-01-16 01:15:12 +03:00
objectClass: top
objectClass: primaryDomain
r11995: A big kerberos-related update.
This merges Samba4 up to current lorikeet-heimdal, which includes a
replacement for some Samba-specific hacks.
In particular, the credentials system now supplies GSS client and
server credentials. These are imported into GSS with
gss_krb5_import_creds(). Unfortunetly this can't take an MEMORY
keytab, so we now create a FILE based keytab as provision and join
time.
Because the keytab is now created in advance, we don't spend .4s at
negprot doing sha1 s2k calls. Also, because the keytab is read in
real time, any change in the server key will be correctly picked up by
the the krb5 code.
To mark entries in the secrets which should be exported to a keytab,
there is a new kerberosSecret objectClass. The new routine
cli_credentials_update_all_keytabs() searches for these, and updates
the keytabs.
This is called in the provision.js via the ejs wrapper
credentials_update_all_keytabs().
We can now (in theory) use a system-provided /etc/krb5.keytab, if
krb5Keytab: FILE:/etc/krb5.keytab
is added to the secrets.ldb record. By default the attribute
privateKeytab: secrets.keytab
is set, pointing to allow the whole private directory to be moved
without breaking the internal links.
(This used to be commit 6b75573df49c6210e1b9d71e108a9490976bd41d)
2005-12-01 08:20:39 +03:00
objectClass: kerberosSecret
2005-03-19 11:11:49 +03:00
flatname: ${DOMAIN}
2005-01-22 02:15:18 +03:00
realm: ${REALM}
2005-07-05 11:10:52 +04:00
secret: ${MACHINEPASS}
2005-05-10 13:49:45 +04:00
secureChannelType: 6
2005-03-23 03:05:44 +03:00
sAMAccountName: ${NETBIOSNAME}$
2005-01-16 01:15:12 +03:00
whenCreated: ${LDAPTIME}
whenChanged: ${LDAPTIME}
2005-06-29 06:28:57 +04:00
msDS-KeyVersionNumber: 1
2005-10-10 02:19:20 +04:00
objectSid: ${DOMAINSID}
r11995: A big kerberos-related update.
This merges Samba4 up to current lorikeet-heimdal, which includes a
replacement for some Samba-specific hacks.
In particular, the credentials system now supplies GSS client and
server credentials. These are imported into GSS with
gss_krb5_import_creds(). Unfortunetly this can't take an MEMORY
keytab, so we now create a FILE based keytab as provision and join
time.
Because the keytab is now created in advance, we don't spend .4s at
negprot doing sha1 s2k calls. Also, because the keytab is read in
real time, any change in the server key will be correctly picked up by
the the krb5 code.
To mark entries in the secrets which should be exported to a keytab,
there is a new kerberosSecret objectClass. The new routine
cli_credentials_update_all_keytabs() searches for these, and updates
the keytabs.
This is called in the provision.js via the ejs wrapper
credentials_update_all_keytabs().
We can now (in theory) use a system-provided /etc/krb5.keytab, if
krb5Keytab: FILE:/etc/krb5.keytab
is added to the secrets.ldb record. By default the attribute
privateKeytab: secrets.keytab
is set, pointing to allow the whole private directory to be moved
without breaking the internal links.
(This used to be commit 6b75573df49c6210e1b9d71e108a9490976bd41d)
2005-12-01 08:20:39 +03:00
privateKeytab: secrets.keytab
2005-10-20 07:47:55 +04:00
2006-01-24 08:31:08 +03:00
# A hook from our credentials system into HDB, as we must be on a KDC,
# we can look directly into the database.
2005-10-20 07:47:55 +04:00
dn: samAccountName=krbtgt,flatname=${DOMAIN},CN=Principals
objectClass: top
objectClass: secret
r11995: A big kerberos-related update.
This merges Samba4 up to current lorikeet-heimdal, which includes a
replacement for some Samba-specific hacks.
In particular, the credentials system now supplies GSS client and
server credentials. These are imported into GSS with
gss_krb5_import_creds(). Unfortunetly this can't take an MEMORY
keytab, so we now create a FILE based keytab as provision and join
time.
Because the keytab is now created in advance, we don't spend .4s at
negprot doing sha1 s2k calls. Also, because the keytab is read in
real time, any change in the server key will be correctly picked up by
the the krb5 code.
To mark entries in the secrets which should be exported to a keytab,
there is a new kerberosSecret objectClass. The new routine
cli_credentials_update_all_keytabs() searches for these, and updates
the keytabs.
This is called in the provision.js via the ejs wrapper
credentials_update_all_keytabs().
We can now (in theory) use a system-provided /etc/krb5.keytab, if
krb5Keytab: FILE:/etc/krb5.keytab
is added to the secrets.ldb record. By default the attribute
privateKeytab: secrets.keytab
is set, pointing to allow the whole private directory to be moved
without breaking the internal links.
(This used to be commit 6b75573df49c6210e1b9d71e108a9490976bd41d)
2005-12-01 08:20:39 +03:00
objectClass: kerberosSecret
2005-10-20 07:47:55 +04:00
flatname: ${DOMAIN}
realm: ${REALM}
sAMAccountName: krbtgt
whenCreated: ${LDAPTIME}
whenChanged: ${LDAPTIME}
objectSid: ${DOMAINSID}
servicePrincipalName: kadmin/changepw
2006-02-04 02:07:58 +03:00
krb5Keytab: HDB:ldb:sam.ldb:
#The trailing : here is a HACK, but it matches the Heimdal format.