oysteikt/heimdal
0
0
Fork 0
Code Issues 5 Pull Requests Releases Activity

x

Browse Source 
git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@13907 ec53bebd-3082-4978-b11e-865c3cabbd6b
This commit is contained in:
Love Hörnquist Åstrand
2004-06-02 14:39:20 +00:00
parent 42b0e3ac77
commit f1cf6dbca2
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/setup.texi
View File

@@ -736,7 +736,8 @@ local transport. For example:
@example @example
access to * access to *
by dn="uid=heimdal,dc=services,dc=padl,dc=com" write by dn.exact="uid=heimdal,dc=services,dc=padl,dc=com" write
...
sasl-regexp "uidNumber=0\\\+gidNumber=.*,cn=peercred,cn=external,cn=auth" sasl-regexp "uidNumber=0\\\+gidNumber=.*,cn=peercred,cn=external,cn=auth"
"uid=heimdal,dc=services,dc=padl,dc=com" "uid=heimdal,dc=services,dc=padl,dc=com"
@@ -748,7 +749,8 @@ a tree. The user that the key is mapped to should be have a
krb5Principal aux object with krb5PrincipalName set so that the krb5Principal aux object with krb5PrincipalName set so that the
``creator'' and ``modifier'' gets right in @file{kadmin}. ``creator'' and ``modifier'' gets right in @file{kadmin}.
Another option is to make an admins group and add the dn to that group. Another option is to create an admins group and add the dn to that
group.
You also needs to make sure its possible for the KDC to connect You also needs to make sure its possible for the KDC to connect
without encryption, the connection is already secure, its done over a without encryption, the connection is already secure, its done over a