From f1cf6dbca2ceb99726858ab38579beaf5a337e14 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Love=20H=C3=B6rnquist=20=C3=85strand?= Date: Wed, 2 Jun 2004 14:39:20 +0000 Subject: [PATCH] x git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@13907 ec53bebd-3082-4978-b11e-865c3cabbd6b --- doc/setup.texi | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/setup.texi b/doc/setup.texi index 2749c6ac3..a868ac41b 100644 --- a/doc/setup.texi +++ b/doc/setup.texi @@ -736,7 +736,8 @@ local transport. For example: @example 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" "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 ``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 without encryption, the connection is already secure, its done over a