Author: buildbot
Date: Mon Jul 30 16:57:58 2012
New Revision: 827431
Log:
Staging update by buildbot for vcl
Modified:
websites/staging/vcl/trunk/content/ (props changed)
websites/staging/vcl/trunk/content/docs/ldapauth.html
Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 30 16:57:58 2012
@@ -1 +1 @@
-1367148
+1367173
Modified: websites/staging/vcl/trunk/content/docs/ldapauth.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/ldapauth.html (original)
+++ websites/staging/vcl/trunk/content/docs/ldapauth.html Mon Jul 30 16:57:58
2012
@@ -291,6 +291,18 @@ Directory LDAP system:</p>
<p>If you add other affiliations that need to be tied in with LDAP, you can
copy this
function and rename things in a similar fashion to match the new LDAP
system.</p>
+<h3 id="some-things-to-be-aware-of-with-mirrored-groups">Some things to be
aware of with mirrored groups</h3>
+<p>There are a few things to be aware of when working with mirrored groups in
VCL. A
+group isn't mirrored in to VCL until someone that is a member of the group
logs in
+to VCL, or a user with the membership is looked up using the <strong>User
Lookup</strong> page.
+So, what is generally suggest is to create an LDAP user that you make a member
of
+all user groups. Then, when you need to get a new group in to VCL, you can
force
+a lookup of that user on the <strong>User Lookup</strong> page. </p>
+<p>The second gotcha is that VCL
+caches a user's LDAP information for up to 24 hours. So, if you log in to VCL,
then add
+yourself to a group on your LDAP server, you will have to wait for up to 24
hours
+before VCL looks up your LDAP information again. Alternatively, you can
+force a lookup on the <strong>User Lookup</strong> page.</p>
</div>
<div id="footer">
