Author: buildbot
Date: Wed Nov 6 02:56:14 2013
New Revision: 885574
Log:
Staging update by buildbot for vcl
Modified:
websites/staging/vcl/trunk/content/ (props changed)
websites/staging/vcl/trunk/content/docs/shibauth.html
Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Nov 6 02:56:14 2013
@@ -1 +1 @@
-1539218
+1539221
Modified: websites/staging/vcl/trunk/content/docs/shibauth.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/shibauth.html (original)
+++ websites/staging/vcl/trunk/content/docs/shibauth.html Wed Nov 6 02:56:14
2013
@@ -72,8 +72,7 @@
<div id="content">
<h1 class="title">Shibboleth Authentication</h1>
- <h1 id="shibboleth-authentication">Shibboleth Authentication</h1>
-<p>The VCL is designed to support Shibboleth authentication for one or more
affiliations. Using Shibboleth
+ <p>The VCL is designed to support Shibboleth authentication for one or
more affiliations. Using Shibboleth
does not preclude the use of LDAP for other affiliations in the same VCL
infrastructure. The principal
advantage of using Shibboleth with the VCL is the ability to completely
externalize authentication
(and, to a certain degree, authorization) decisions. That is, by using
Shibboleth authentication, a user's
