Author: olamy
Date: Thu Jan 3 17:16:03 2013
New Revision: 1428488
URL: http://svn.apache.org/viewvc?rev=1428488&view=rev
Log:
Apache Redback Main site deployment
Modified:
archiva/site-content/redback/development/extending-authn.html
archiva/site-content/redback/integration/ldap.html
Modified: archiva/site-content/redback/development/extending-authn.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/development/extending-authn.html?rev=1428488&r1=1428487&r2=1428488&view=diff
==============================================================================
--- archiva/site-content/redback/development/extending-authn.html (original)
+++ archiva/site-content/redback/development/extending-authn.html Thu Jan 3
17:16:03 2013
@@ -199,7 +199,7 @@ pageTracker._trackPageview();</script>
<div id="bodyColumn" >
- <!-- Licensed to the Apache Software Foundation (ASF) under one
--><!-- or more contributor license agreements. See the NOTICE file --><!--
distributed with this work for additional information --><!-- regarding
copyright ownership. The ASF licenses this file --><!-- to you under the
Apache License, Version 2.0 (the --><!-- "License"); you may not use this file
except in compliance --><!-- with the License. You may obtain a copy of the
License at --><!-- --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--
--><!-- Unless required by applicable law or agreed to in writing, --><!--
software distributed under the License is distributed on an --><!-- "AS IS"
BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or
implied. See the License for the --><!-- specific language governing
permissions and limitations --><!-- under the License. --><!-- NOTE: For help
with the syntax of this file, see: --><!-- http://maven.apache.org/guides/mi
ni/guide-apt-format.html --><div class="section"><h2>Extending Redback
Authentication<a name="Extending_Redback_Authentication"></a></h2><p>In order
to accomodate the many authentication security services used in various
applications, it is possible to to implement pluggable authentication providers
in the Redback security system.</p><div class="section"><h3>Requirements<a
name="Requirements"></a></h3><ul><li><tt>redback-authentication-api</tt> must
be implemented<ul><li>create an authentication implementation project under
<tt>redback-authentication-providers</tt></li><li><tt>org.apache.archiva.redback.authentication.Authenticator</tt>
must be implemented</li></ul></li><li><tt>redback-users-api</tt> must be
implemented<ul><li>create a user provider implementation project under
<tt>redback-users-providers</tt></li><li><tt>org.apache.archiva.redback.users.User</tt>
must be
implemented</li><li><tt>org.apache.archiva.redback.users.UserManager</tt> must
be implemented</li></ul><
/li><li>utility and wrapper classes can be implemented under
<tt>redback-common</tt><ul><li>e.g.
<tt>$redback/redback-common/redback-common-ldap</tt> contains the utility class
<tt>org.apache.archiva.redback.common.ldap.LdapUtils</tt>, and the wrapper
class <tt>org.apache.archiva.redback.common.ldap.LdapUser</tt></li><li>other
essential classes may be placed here as well, such as the
<tt>org.apache.archiva.redback.common.ldap.connection.LdapConnectionFactory</tt></li></ul></li></ul></div><div
class="section"><h3>Examples<a name="Examples"></a></h3><div
class="section"><h4>Implementing OpenId (<a class="externalLink"
href="http://wiki.openid.net/";>OpenId Homepage</a>)<a
name="Implementing_OpenId_OpenId_Homepage"></a></h4><p>While OpenId may be
directly integrated to the authentication point of the web application, another
option is to implement the redback api.</p><p>Here is something to get
started:</p><ul><li>create the provider project
<tt>redback-authentication-openid</tt
><ul><li>create the authenticator class, something like
><tt>OpenIdAuthenticator</tt> that implements
><tt>org.apache.archiva.redback.authentication.Authenticator</tt></li></ul></li><li>create
> the provider project <tt>redback-users-openid</tt><ul><li>implement
><tt>org.apache.archiva.redback.users.User</tt>, something like
><tt>OpenIdUser</tt><ul><li>OpenId supports only the principal/username and
>password fields, so use dummy/default values for the unsupported fields
>(email, fullname) in this case.</li></ul></li><li>implement
><tt>org.apache.archiva.redback.users.UserManager</tt>, something like
><tt>OpenIdUserManager</tt><ul><li>OpenId is a read-only authentication
>service, <tt>createUser()</tt>, <tt>updateUser()</tt>, <tt>deleteUser()</tt>
>may not be used</li></ul></li><li>various utility classes may be implemented
>in <tt>redback-common-openid</tt><ul><li><tt>OpenIdConfiguration</tt> may be
>used to encapsulate the following configuration properties (properties that
>may be speci
fied in the <tt>security.properties</tt>
file):<ul><li><tt>openid.config.provider.url</tt>, where this is a url to one
openid provider (support to many providers may come later, specified or via
discovery, depending on the organization's security
policy)</li></ul></li><li><tt>OpenIdUtils</tt> class, may be implemented to
normalize the User-Supplied Identifier to an Identifier that the OpenId
Provider understands, e.g. redback username ('<tt>johndoe</tt>') to OpenId
url-like identifier
('<tt>http://johndoe.openidprovider.com</tt>')</li><li><tt>OpenIdAuthenticationException</tt>
that implements
<tt>org.apache.archiva.redback.authentication.AuthenticationException</tt></li><li><tt>OpenIdProviderFactory</tt>
that takes the configuration from
<tt>OpenIdConfiguration</tt></li><li><tt>OpenIdProvider</tt> is where the
<tt>OpenIdUserManager</tt> can verify a
user</li></ul></li></ul></li></ul></div></div></div>
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
--><!-- or more contributor license agreements. See the NOTICE file --><!--
distributed with this work for additional information --><!-- regarding
copyright ownership. The ASF licenses this file --><!-- to you under the
Apache License, Version 2.0 (the --><!-- "License"); you may not use this file
except in compliance --><!-- with the License. You may obtain a copy of the
License at --><!-- --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--
--><!-- Unless required by applicable law or agreed to in writing, --><!--
software distributed under the License is distributed on an --><!-- "AS IS"
BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or
implied. See the License for the --><!-- specific language governing
permissions and limitations --><!-- under the License. --><!-- NOTE: For help
with the syntax of this file, see: --><!-- http://maven.apache.org/guides/mi
ni/guide-apt-format.html --><div class="section"><h2>Extending Redback
Authentication<a name="Extending_Redback_Authentication"></a></h2><p>In order
to accomodate the many authentication security services used in various
applications, it is possible to to implement pluggable authentication providers
in the Redback security system.</p><div class="section"><h3>Requirements<a
name="Requirements"></a></h3><ul><li><tt>redback-authentication-api</tt> must
be implemented<ul><li>create an authentication implementation project under
<tt>redback-authentication-providers</tt></li><li><tt>org.apache.archiva.redback.authentication.Authenticator</tt>
must be implemented</li></ul></li><li><tt>redback-users-api</tt> must be
implemented<ul><li>create a user provider implementation project under
<tt>redback-users-providers</tt></li><li><tt>org.apache.archiva.redback.users.User</tt>
must be
implemented</li><li><tt>org.apache.archiva.redback.users.UserManager</tt> must
be implemented</li></ul><
/li><li>utility and wrapper classes can be implemented under
<tt>redback-common</tt><ul><li>e.g.
<tt>$redback/redback-common/redback-common-ldap</tt> contains the utility class
<tt>org.apache.archiva.redback.common.ldap.LdapUtils</tt>, and the wrapper
class
<tt>org.apache.archiva.redback.common.ldap.user.LdapUser</tt></li><li>other
essential classes may be placed here as well, such as the
<tt>org.apache.archiva.redback.common.ldap.connection.LdapConnectionFactory</tt></li></ul></li></ul></div><div
class="section"><h3>Examples<a name="Examples"></a></h3><div
class="section"><h4>Implementing OpenId (<a class="externalLink"
href="http://wiki.openid.net/";>OpenId Homepage</a>)<a
name="Implementing_OpenId_OpenId_Homepage"></a></h4><p>While OpenId may be
directly integrated to the authentication point of the web application, another
option is to implement the redback api.</p><p>Here is something to get
started:</p><ul><li>create the provider project <tt>redback-authentication-openi
d</tt><ul><li>create the authenticator class, something like
<tt>OpenIdAuthenticator</tt> that implements
<tt>org.apache.archiva.redback.authentication.Authenticator</tt></li></ul></li><li>create
the provider project <tt>redback-users-openid</tt><ul><li>implement
<tt>org.apache.archiva.redback.users.User</tt>, something like
<tt>OpenIdUser</tt><ul><li>OpenId supports only the principal/username and
password fields, so use dummy/default values for the unsupported fields (email,
fullname) in this case.</li></ul></li><li>implement
<tt>org.apache.archiva.redback.users.UserManager</tt>, something like
<tt>OpenIdUserManager</tt><ul><li>OpenId is a read-only authentication service,
<tt>createUser()</tt>, <tt>updateUser()</tt>, <tt>deleteUser()</tt> may not be
used</li></ul></li><li>various utility classes may be implemented in
<tt>redback-common-openid</tt><ul><li><tt>OpenIdConfiguration</tt> may be used
to encapsulate the following configuration properties (properties that may be
specified in the <tt>security.properties</tt>
file):<ul><li><tt>openid.config.provider.url</tt>, where this is a url to one
openid provider (support to many providers may come later, specified or via
discovery, depending on the organization's security
policy)</li></ul></li><li><tt>OpenIdUtils</tt> class, may be implemented to
normalize the User-Supplied Identifier to an Identifier that the OpenId
Provider understands, e.g. redback username ('<tt>johndoe</tt>') to OpenId
url-like identifier
('<tt>http://johndoe.openidprovider.com</tt>')</li><li><tt>OpenIdAuthenticationException</tt>
that implements
<tt>org.apache.archiva.redback.authentication.AuthenticationException</tt></li><li><tt>OpenIdProviderFactory</tt>
that takes the configuration from
<tt>OpenIdConfiguration</tt></li><li><tt>OpenIdProvider</tt> is where the
<tt>OpenIdUserManager</tt> can verify a
user</li></ul></li></ul></li></ul></div></div></div>
</div>
</div>
Modified: archiva/site-content/redback/integration/ldap.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/integration/ldap.html?rev=1428488&r1=1428487&r2=1428488&view=diff
==============================================================================
--- archiva/site-content/redback/integration/ldap.html (original)
+++ archiva/site-content/redback/integration/ldap.html Thu Jan 3 17:16:03 2013
@@ -205,7 +205,7 @@ pageTracker._trackPageview();</script>
<property name="userConf"
ref="userConfiguration"/>
</bean>
</pre></div><p>In security.properties
files</p><ul><li>ldap.config.hostname - The hostname of the ldap
server</li><li>ldap.config.port - The port of the ldap
server</li><li>ldap.config.base.dn - The baseDn of the ldap
system</li><li>ldap.config.context.factory - context factory for ldap
connections (com.sun.jndi.ldap.LdapCtxFactory)</li><li>ldap.config.password -
password for the bindDn for the root ldap
connection</li><li>ldap.config.bind.dn - the core user used for authentication
the ldap server, must be able to perform the necessary searches,
etc.</li></ul></div><div class="section"><h5>user mapper<a
name="user_mapper"></a></h5><div class="source"><pre class="prettyprint">
- <bean name="ldapUserMapper"
class="org.apache.archiva.redback.common.ldap.LdapUserMapper">
+ <bean name="ldapUserMapper"
class="org.apache.archiva.redback.common.ldap.user.LdapUserMapper">
<property name="emailAttribute" value="email"/>
<property name="fullNameAttribute"
value="givenName"/>
<property name="passwordAttribute"
value="userPassword"/>
