Author: olamy
Date: Wed Apr 8 11:24:28 2015
New Revision: 1672063
URL: http://svn.apache.org/r1672063
Log:
checking
Modified:
archiva/site-content/redback/authentication.html
archiva/site-content/redback/authorization.html
archiva/site-content/redback/configuration.html
archiva/site-content/redback/development/extending-authn.html
archiva/site-content/redback/errors/404.html
archiva/site-content/redback/index.html
archiva/site-content/redback/integration.html
archiva/site-content/redback/integration/ldap.html
archiva/site-content/redback/integration/rest.html
archiva/site-content/redback/issue-tracking.html
archiva/site-content/redback/key-store.html
archiva/site-content/redback/license.html
archiva/site-content/redback/mail-lists.html
archiva/site-content/redback/privacy-policy.html
archiva/site-content/redback/project-info.html
archiva/site-content/redback/rbac/introduction.html
archiva/site-content/redback/rbac/role-management.html
archiva/site-content/redback/source-repository.html
archiva/site-content/redback/team-list.html
archiva/site-content/redback/user-management.html
Modified: archiva/site-content/redback/authentication.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/authentication.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/authentication.html (original)
+++ archiva/site-content/redback/authentication.html Wed Apr 8 11:24:28 2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Authentication</title>
+ <title>Apache Redback – Authentication</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -206,7 +206,7 @@
<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/mini/guide
-apt-format.html --><div class="section">
-<h2>Redback Authentication<a name="Redback_Authentication"></a></h2>
+<h2><a name="Redback_Authentication"></a>Redback Authentication</h2>
<p>Redback currently supports the following authentication mechanisms:</p>
<ul>
<li>username/password for redback-users </li>
@@ -223,7 +223,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/authorization.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/authorization.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/authorization.html (original)
+++ archiva/site-content/redback/authorization.html Wed Apr 8 11:24:28 2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Authorization</title>
+ <title>Apache Redback – Authorization</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -206,7 +206,7 @@
<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/mini/guide
-apt-format.html --><div class="section">
-<h2>Redback Authorization<a name="Redback_Authorization"></a></h2>
+<h2><a name="Redback_Authorization"></a>Redback Authorization</h2>
<p>Redback comes with an implementation of role based access control. Please
see the section below on rbac to learn more about that system.</p></div>
</div>
</div>
@@ -216,7 +216,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/configuration.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/configuration.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/configuration.html (original)
+++ archiva/site-content/redback/configuration.html Wed Apr 8 11:24:28 2015
@@ -1,5 +1,4 @@
<!DOCTYPE html>
-
<!--
| Generated by Apache Maven Doxia
| Rendered using Apache Maven Fluido Skin 1.3.1
@@ -8,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Configuration</title>
+ <title>Apache Redback – Configuration</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
@@ -181,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -207,7 +206,7 @@
<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/mini/guide
-apt-format.html --><div class="section">
-<h2>Redback Configuration<a name="Redback_Configuration"></a></h2>
+<h2><a name="Redback_Configuration"></a>Redback Configuration</h2>
<p>Configuration in Redback is governed by a plexus configuration setup making
use of properties files. Below is a listing of all of the available
configuration options along with default values and notes on what they are
where applicable.</p>
<ul>
<li><a href="#Redback_Configuration">Redback Configuration</a>
@@ -228,7 +227,7 @@
<li><a href="#User_Manager_Implementations_to_use">User Manager
Implementation(s) to use</a></li>
<li><a href="#RBAC_Manager_Implementations_to_use">RBAC Manager
Implementation(s) to use</a></li></ul></li></ul></li></ul>
<div class="section">
-<h3>Configuration File Locations<a
name="Configuration_File_Locations"></a></h3>
+<h3><a name="Configuration_File_Locations"></a>Configuration File
Locations</h3>
<p>Configuration file location can depend on the application that is embedding
Redback. Since Redback is currently built up off of Plexus, it would be ideal
to check out the application.xml of the relevant application and look for an
entry similar to the following.</p>
<div>
<pre>
@@ -245,16 +244,16 @@
</bean>
</pre></div></div>
<div class="section">
-<h3>Configuration Options<a name="Configuration_Options"></a></h3>
+<h3><a name="Configuration_Options"></a>Configuration Options</h3>
<div class="section">
-<h4>Application Configuration<a name="Application_Configuration"></a></h4>
+<h4><a name="Application_Configuration"></a>Application Configuration</h4>
<ul>
<li>application.timestamp=EEE d MMM yyyy HH:mm:ss Z</li>
<li>application.url=http://myurl.mycompany.com
<ul>
<li>Set the application base URL. The default is to derive it from the HTTP
request</li></ul></li></ul></div>
<div class="section">
-<h4>JDBC Setup<a name="JDBC_Setup"></a></h4>
+<h4><a name="JDBC_Setup"></a>JDBC Setup</h4>
<p>By default Redback uses Apache Derby for persistence of user and role
information. This can be configured with the following options.</p>
<ul>
<li>jdbc.driver.name=org.apache.derby.jdbc.EmbeddedDriver</li>
@@ -264,7 +263,7 @@
<p>By default Redback uses Apache Derby for persistence of user and role
information. This can be configured with the following options.</p>
<p><b>Note:</b> If you are using MySQL as your database, the database will not
be populated if the encoding is initially set to UTF-8. As a workaround, set
the database to UTF-8 encoding after it has been populated. See <a
class="externalLink" href="http://jira.codehaus.org/browse/REDBACK-267";>
REDBACK-267</a> for more details.</p></div>
<div class="section">
-<h4>Email Settings<a name="Email_Settings"></a></h4>
+<h4><a name="Email_Settings"></a>Email Settings</h4>
<ul>
<li>email.jndiSessionName=java:comp/env/mail/Session</li>
<li>email.smtp.host=localhost</li>
@@ -290,7 +289,7 @@
<li>Get the Feedback to use for any outgoing emails.</li>
<li>Feedback path starts with a "/" it is appended to the end of the
value provided in application.url. This value can be in the format/syntax of
"/feedback.action" or even
"mailto:[email protected]"</li></ul></li></ul></div>
<div class="section">
-<h4>Auto Login Settings<a name="Auto_Login_Settings"></a></h4>
+<h4><a name="Auto_Login_Settings"></a>Auto Login Settings</h4>
<ul>
<li>security.rememberme.enabled=true</li>
<li>security.rememberme.timeout=365
@@ -301,7 +300,7 @@
<li>Single Sign On</li>
<li>Timeout is in minutes</li></ul></li></ul></div>
<div class="section">
-<h4>Default Username Values<a name="Default_Username_Values"></a></h4>
+<h4><a name="Default_Username_Values"></a>Default Username Values</h4>
<ul>
<li>redback.default.admin=admin
<ul>
@@ -310,7 +309,7 @@
<ul>
<li>name of the guest user</li></ul></li></ul></div>
<div class="section">
-<h4>Security Policies<a name="Security_Policies"></a></h4>
+<h4><a name="Security_Policies"></a>Security Policies</h4>
<ul>
<li>security.policy.password.encoder=</li>
<li>security.policy.password.previous.count=6</li>
@@ -328,7 +327,7 @@
<ul>
<li>can be specified multiple times to ensure that password policies never
lock the specified account(s) (eg. security.policy.unlockable.accounts=guest
)</li></ul></li></ul></div>
<div class="section">
-<h4>Password Rules<a name="Password_Rules"></a></h4>
+<h4><a name="Password_Rules"></a>Password Rules</h4>
<ul>
<li>security.policy.password.rule.alphanumeric.enabled=false</li>
<li>security.policy.password.rule.alphacount.enabled=true</li>
@@ -342,13 +341,13 @@
<li>security.policy.password.rule.reuse.enabled=true</li>
<li>security.policy.password.rule.nowhitespace.enabled=true</li></ul></div>
<div class="section">
-<h4>LDAP settings<a name="LDAP_settings"></a></h4>
+<h4><a name="LDAP_settings"></a>LDAP settings</h4>
<p>Ldap can be used as a readonly user manager, however the role assignment is
still managed entirely within the given database store. This should be fixed in
the future sometime but likely not before ldap is switched over as the default
user and role store entirely.</p>
<ul>
<li>ldap.user.store.enabled=false</li>
<li>ldap.bind.authenticator.enabled=false</li></ul>
<div class="section">
-<h5>ldap options for configuration via properties file<a
name="ldap_options_for_configuration_via_properties_file"></a></h5>
+<h5><a name="ldap_options_for_configuration_via_properties_file"></a>ldap
options for configuration via properties file</h5>
<ul>
<li>ldap.config.hostname=</li>
<li>ldap.config.port=</li>
@@ -364,13 +363,13 @@
<li>ldap.config.groups.use.rolename=true/false will create/use groups in ldap
with default role if no group<i>-</i>role mapping found (default false)</li>
<li>ldap.config.user.attribute= attribute name to use for user (default
uid=)</li></ul></div></div>
<div class="section">
-<h4>User Manager Implementation(s) to use<a
name="User_Manager_Implementations_to_use"></a></h4>
+<h4><a name="User_Manager_Implementations_to_use"></a>User Manager
Implementation(s) to use</h4>
<ul>
<li>user.manager.impl=cached (since 1.4-M4: Archiva support more than one
value comma separated)
<ul>
<li>valid values for realistic usage are 'cached' and then further configuring
the cached instance to use another underlying user manager like ldap or the jdo
one which is used by default. Placing 'ldap' here will check with the ldap
system for a fair amount of checks and would likely be a performance
issue</li></ul></li></ul></div>
<div class="section">
-<h4>RBAC Manager Implementation(s) to use<a
name="RBAC_Manager_Implementations_to_use"></a></h4>
+<h4><a name="RBAC_Manager_Implementations_to_use"></a>RBAC Manager
Implementation(s) to use</h4>
<ul>
<li>rbac.manager.impl=cached (since 1.4-M4: Archiva support more than one
value comma separated)</li></ul></div></div></div>
</div>
@@ -381,7 +380,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
@@ -411,4 +410,4 @@
</div>
</footer>
</body>
-</html>
+</html>
\ No newline at end of file
Modified: archiva/site-content/redback/development/extending-authn.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/development/extending-authn.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/development/extending-authn.html (original)
+++ archiva/site-content/redback/development/extending-authn.html Wed Apr 8
11:24:28 2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Development</title>
+ <title>Apache Redback – Development</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
<link rel="stylesheet" href="../css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -206,10 +206,10 @@
<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/mini/guide
-apt-format.html --><div class="section">
-<h2>Extending Redback Authentication<a
name="Extending_Redback_Authentication"></a></h2>
+<h2><a name="Extending_Redback_Authentication"></a>Extending Redback
Authentication</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>
+<h3><a name="Requirements"></a>Requirements</h3>
<ul>
<li><tt>redback-authentication-api</tt> must be implemented
<ul>
@@ -225,9 +225,9 @@
<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>
+<h3><a name="Examples"></a>Examples</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>
+<h4><a name="Implementing_OpenId_OpenId_Homepage"></a>Implementing OpenId (<a
class="externalLink" href="http://wiki.openid.net/";>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>
@@ -259,7 +259,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/errors/404.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/errors/404.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/errors/404.html (original)
+++ archiva/site-content/redback/errors/404.html Wed Apr 8 11:24:28 2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Page Not found</title>
+ <title>Apache Redback – Page Not found</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
<link rel="stylesheet" href="../css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -206,7 +206,7 @@
<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/mini/guide
-apt-format.html --><div class="section">
-<h2>Page Not Found<a name="Page_Not_Found"></a></h2>
+<h2><a name="Page_Not_Found"></a>Page Not Found</h2>
<p>We're sorry, but the page you requested cannot be found. This may be
because:</p>
<ul>
<li>The page has moved, was outdated, or has not been created yet</li>
@@ -221,7 +221,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/index.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/index.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/index.html (original)
+++ archiva/site-content/redback/index.html Wed Apr 8 11:24:28 2015
@@ -8,9 +8,9 @@
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="Date-Creation-yyyymmdd" content="20121123" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Introduction</title>
+ <title>Apache Redback – Introduction</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
@@ -181,7 +181,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -207,7 +207,7 @@
<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/mini/guide
-apt-format.html --><div class="section">
-<h2>Introduction<a name="Introduction"></a></h2>
+<h2><a name="Introduction"></a>Introduction</h2>
<p>Apache Redback started as an attempt to clean away some of the more
annoying security related components of web applications and centralize them
into a simple to use framework. Some of the basic beliefs we started with where
that authentication, authorization and user management were all basically
seperate concerns, sure there are points where they rub up against each other
but those are pretty clear points and not worth mashing up whole discrete
concepts together.</p>
<p>Redback supports a number of authentication mechanisms, and a couple of
authorization schemes including an implementation of role based access control.
Redback has been built on top of the plexus container so it is simple to have
the core security system object into your code for making authentication,
authorization or user management tasks through its api.</p>
<p>Apache Redback is currently being used for providing a consistent security
related user experience to Apache Continuum and Archiva.</p></div>
@@ -219,7 +219,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/integration.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/integration.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/integration.html (original)
+++ archiva/site-content/redback/integration.html Wed Apr 8 11:24:28 2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Continuous Integration</title>
+ <title>Apache Redback – Continuous Integration</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -206,15 +206,15 @@
<div id="bodyColumn" >
<div class="section">
-<h2>Overview<a name="Overview"></a></h2><a name="Overview"></a>
+<h2><a name="Overview"></a>Overview</h2><a name="Overview"></a>
<p>This project uses <a class="externalLink"
href="http://jenkins-ci.org/";>Jenkins</a>.</p></div>
<div class="section">
-<h2>Access<a name="Access"></a></h2><a name="Access"></a>
+<h2><a name="Access"></a>Access</h2><a name="Access"></a>
<p>The following is a link to the continuous integration system used by the
project.</p>
<div class="source">
<pre><a class="externalLink"
href="https://builds.apache.org/view/A-F/view/Archiva/";>https://builds.apache.org/view/A-F/view/Archiva/</a></pre></div></div>
<div class="section">
-<h2>Notifiers<a name="Notifiers"></a></h2><a name="Notifiers"></a>
+<h2><a name="Notifiers"></a>Notifiers</h2><a name="Notifiers"></a>
<p>No notifiers are defined. Please check back at a later date.</p></div>
</div>
</div>
@@ -224,7 +224,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/integration/ldap.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/integration/ldap.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/integration/ldap.html (original)
+++ archiva/site-content/redback/integration/ldap.html Wed Apr 8 11:24:28 2015
@@ -8,9 +8,9 @@
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="Date-Creation-yyyymmdd" content="20121123" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Ldap Integration</title>
+ <title>Apache Redback – Ldap Integration</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
<link rel="stylesheet" href="../css/print.css" media="print" />
@@ -181,7 +181,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -207,20 +207,20 @@
<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/mini/guide
-apt-format.html --><div class="section">
-<h2>Redback Ldap Integration<a name="Redback_Ldap_Integration"></a></h2>
+<h2><a name="Redback_Ldap_Integration"></a>Redback Ldap Integration</h2>
<p>Redback has limited support for ldap has been added as an authentication
source. Limited support for ldap means:</p>
<ul>
<li>Read-Only User Management</li>
<li>xml and properties based configuration</li>
<li>tested against open ldap on linux and <a class="externalLink"
href="http://directory.apache.org";>apacheds</a> 1.5.0/2.0.0 and <a
class="externalLink" href="http://opendj.forgerock.org";>OpenDj</a></li></ul>
<div class="section">
-<h3>Setting up Ldap<a name="Setting_up_Ldap"></a></h3>
+<h3><a name="Setting_up_Ldap"></a>Setting up Ldap</h3>
<p>Configuration for ldap is actually a relatively simple procedure, a few
components definitions need to be declared in an appropriate application.xml
and then some configuration options must be set in the security.properties
file.</p>
<div class="section">
-<h4>The applicationContext.xml Additions<a
name="The_applicationContext.xml_Additions"></a></h4>
+<h4><a name="The_applicationContext.xml_Additions"></a>The
applicationContext.xml Additions</h4>
<p>These components should be defined in the applicable spring configuration
files</p>
<div class="section">
-<h5>ldap connection factory <a name="ldap_connection_factory"></a></h5>
+<h5><a name="ldap_connection_factory"></a>ldap connection factory </h5>
<div class="source">
<pre>
<bean name="ldapConnectionFactory"
class="org.apache.archiva.redback.common.ldap.connection.ConfigurableLdapConnectionFactory">
@@ -236,7 +236,7 @@
<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>
+<h5><a name="user_mapper"></a>user mapper</h5>
<div class="source">
<pre>
<bean name="ldapUserMapper"
class="org.apache.archiva.redback.common.ldap.user.LdapUserMapper">
@@ -259,7 +259,7 @@
<li>ldap.config.mapper.attribute.user.object.class - the objectClass used in
the ldap server for indentifying users, most commonly inetOrgPerson.</li>
<li>ldap.config.mapper.attribute.user.filter - the user filter is used to
reduce the number of results during a LDAP request. It is
optional.</li></ul></div>
<div class="section">
-<h5>security policy (for the password encoder) <a
name="security_policy_for_the_password_encoder"></a></h5>
+<h5><a name="security_policy_for_the_password_encoder"></a>security policy
(for the password encoder) </h5>
<div class="source">
<pre>
<bean name="userSecurityPolicy"
class="org.apache.archiva.redback.policy.DefaultUserSecurityPolicy">
@@ -282,7 +282,7 @@
</bean>
</pre></div></div></div></div>
<div class="section">
-<h3>security.properties<a name="security.properties"></a></h3>
+<h3><a name="security.properties"></a>security.properties</h3>
<p>These properties should be set as shown:</p>
<div class="source">
<pre>
@@ -297,7 +297,7 @@ security.policy.password.expiration.enab
<p>It is also now possible to redefine the basic admin user and guest user
names. Since its unlikely that ldap oriented authentication systems will have a
specific admin or guest user these can be redefined simply in the
security.properties. Care must be taken that they exist in the ldap system
since they are looked up. Guest users can be simple utilitie or application
users.</p>
<p>The final setting of security.policy.password.expiration.enabled is a
boolean that should be set to false for ldap based authentication. This is
because redback will want to attempt to manage and enforce password expiration
and that is no longer under the direction of redback but is an artifact of the
ldap system in place. Setting this to false prevents issues from cropping up
related to redback trying to obtain this type of information.</p></div>
<div class="section">
-<h3>Caching<a name="Caching"></a></h3>
+<h3><a name="Caching"></a>Caching</h3>
<p>A cache named 'ldapUser' is used to reduce access to the LDAP server.</p>
<p>Pooled connection are enabled per default using the properties <a
class="externalLink"
href="http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/pool.html";>ldap
pooling</a>:</p>
<ul>
@@ -312,7 +312,7 @@ security.policy.password.expiration.enab
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/integration/rest.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/integration/rest.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/integration/rest.html (original)
+++ archiva/site-content/redback/integration/rest.html Wed Apr 8 11:24:28 2015
@@ -9,9 +9,9 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="Olivier Lamy" />
<meta name="Date-Creation-yyyymmdd" content="20110811" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Redback Rest Support</title>
+ <title>Apache Redback – Redback Rest Support</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
<link rel="stylesheet" href="../css/print.css" media="print" />
@@ -182,7 +182,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -208,11 +208,11 @@
<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/doxia/references/
apt-format.html --><div class="section">
-<h2>Redback Rest Support<a name="Redback_Rest_Support"></a></h2>
+<h2><a name="Redback_Rest_Support"></a>Redback Rest Support</h2>
<p>Prior to 1.3 version some redback services are available trough rest
request.</p>
<p>We use jaxrs annotations and authz/karma are verified through cxf
interceptors.</p>
<div class="section">
-<h3>Maven Module<a name="Maven_Module"></a></h3>
+<h3><a name="Maven_Module"></a>Maven Module</h3>
<p>You must add the following maven dependency</p>
<div class="source">
<pre>
@@ -223,7 +223,7 @@
</dependency>
</pre></div></div>
<div class="section">
-<h3>CXF setup<a name="CXF_setup"></a></h3>
+<h3><a name="CXF_setup"></a>CXF setup</h3>
<p>The spring file is in the redback-rest-services module. You must add
META-INF/spring-context.xml in your spring configuration.</p>
<p>And add cxf servlet in your web.xml :</p>
<div class="source">
@@ -240,7 +240,7 @@
</servlet-mapping>
</pre></div></div>
<div class="section">
-<h3>CXF interceptors<a name="CXF_interceptors"></a></h3>
+<h3><a name="CXF_interceptors"></a>CXF interceptors</h3>
<p>Rest services are declared as it in the cxf configuration :</p>
<div class="source">
<pre>
@@ -256,10 +256,10 @@
</jaxrs:server>
</pre></div>
<div class="section">
-<h4>AuthenticationInterceptor<a name="AuthenticationInterceptor"></a></h4>
+<h4><a name="AuthenticationInterceptor"></a>AuthenticationInterceptor</h4>
<p>This interceptor is basic on HTTP BASIC authz with using
HttpBasicAuthentication spring component.</p></div>
<div class="section">
-<h4>PermissionInterceptor<a name="PermissionInterceptor"></a></h4>
+<h4><a name="PermissionInterceptor"></a>PermissionInterceptor</h4>
<p>This inceptor will use a new created annotation named @RedbackAuthorization
which supports attributes : permissions, resource and noRestriction.</p>
<p>You can use it :</p>
<div class="source">
@@ -275,7 +275,7 @@
public Boolean ping()
</pre></div></div></div>
<div class="section">
-<h3>Client Usage<a name="Client_Usage"></a></h3>
+<h3><a name="Client_Usage"></a>Client Usage</h3>
<p>Dependencies to add in order to use those REST Services</p>
<div class="source">
<pre>
@@ -312,7 +312,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/issue-tracking.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/issue-tracking.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/issue-tracking.html (original)
+++ archiva/site-content/redback/issue-tracking.html Wed Apr 8 11:24:28 2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Issue Tracking</title>
+ <title>Apache Redback – Issue Tracking</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -206,13 +206,13 @@
<div id="bodyColumn" >
<div class="section">
-<h2>Overview<a name="Overview"></a></h2><a name="Overview"></a>
+<h2><a name="Overview"></a>Overview</h2><a name="Overview"></a>
<p>This project uses <a class="externalLink"
href="http://www.atlassian.com/software/jira";>JIRA</a> a J2EE-based, issue
tracking and project management application.</p></div>
<div class="section">
-<h2>Issue Tracking<a name="Issue_Tracking"></a></h2><a
name="Issue_Tracking"></a>
+<h2><a name="Issue_Tracking"></a>Issue Tracking</h2><a
name="Issue_Tracking"></a>
<p>Issues, bugs, and feature requests should be submitted to the following
issue tracking system for this project.</p>
<div class="source">
-<pre><a class="externalLink"
href="http://jira.codehaus.org/browse/MRM";>http://jira.codehaus.org/browse/MRM</a></pre></div></div>
+<pre><a class="externalLink"
href="https://issues.apache.org/jira/browse/MRM";>https://issues.apache.org/jira/browse/MRM</a></pre></div></div>
</div>
</div>
@@ -221,7 +221,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/key-store.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/key-store.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/key-store.html (original)
+++ archiva/site-content/redback/key-store.html Wed Apr 8 11:24:28 2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Keystore</title>
+ <title>Apache Redback – Keystore</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -206,7 +206,7 @@
<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/mini/guide
-apt-format.html --><div class="section">
-<h2>Redback Keystores<a name="Redback_Keystores"></a></h2>
+<h2><a name="Redback_Keystores"></a>Redback Keystores</h2>
<p>Redback comes with a keystore implementation for authenticating based on
unique keys. This implemention is currently used for authenticating single on
for multiple applications sharing a security setup as well as remember me
functionalities for website type login scenarios.</p>
<p>The redback keystore is currently implemented using jpox and has support
for multiple databases.</p></div>
</div>
@@ -217,7 +217,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/license.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/license.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/license.html (original)
+++ archiva/site-content/redback/license.html Wed Apr 8 11:24:28 2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Project License</title>
+ <title>Apache Redback – Project License</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -205,12 +205,12 @@
<div id="bodyColumn" >
<div class="section">
-<h2>Overview<a name="Overview"></a></h2><a name="Overview"></a>
+<h2><a name="Overview"></a>Overview</h2><a name="Overview"></a>
<p>Typically the licenses listed for the project are that of the project
itself, and not of dependencies.</p></div>
<div class="section">
-<h2>Project License<a name="Project_License"></a></h2><a
name="Project_License"></a>
+<h2><a name="Project_License"></a>Project License</h2><a
name="Project_License"></a>
<div class="section">
-<h3>The Apache Software License, Version 2.0<a
name="The_Apache_Software_License_Version_2.0"></a></h3><a
name="The_Apache_Software_License_Version_2.0"></a>
+<h3><a name="The_Apache_Software_License_Version_2.0"></a>The Apache Software
License, Version 2.0</h3><a name="The_Apache_Software_License_Version_2.0"></a>
<div class="source">
<pre>
Apache License
@@ -423,7 +423,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/mail-lists.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/mail-lists.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/mail-lists.html (original)
+++ archiva/site-content/redback/mail-lists.html Wed Apr 8 11:24:28 2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Project Mailing Lists</title>
+ <title>Apache Redback – Project Mailing Lists</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -206,7 +206,7 @@
<div id="bodyColumn" >
<div class="section">
-<h2>Project Mailing Lists<a name="Project_Mailing_Lists"></a></h2><a
name="Project_Mailing_Lists"></a>
+<h2><a name="Project_Mailing_Lists"></a>Project Mailing Lists</h2><a
name="Project_Mailing_Lists"></a>
<p>These are the mailing lists that have been established for this project.
For each list, there is a subscribe, unsubscribe, and an archive link.</p>
<table border="0" class="table table-striped">
<tr class="a">
@@ -308,7 +308,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/privacy-policy.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/privacy-policy.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/privacy-policy.html (original)
+++ archiva/site-content/redback/privacy-policy.html Wed Apr 8 11:24:28 2015
@@ -9,9 +9,9 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="Vincent Siveton" />
<meta name="Date-Creation-yyyymmdd" content="20081203" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Privacy Policy</title>
+ <title>Apache Redback – Privacy Policy</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
@@ -182,7 +182,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -208,7 +208,7 @@
<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. --><div class="section">
-<h2>Privacy Policy<a name="Privacy_Policy"></a></h2>
+<h2><a name="Privacy_Policy"></a>Privacy Policy</h2>
<p>Information about your use of this website is collected using server access
logs and a tracking cookie. The collected information consists of the
following:</p>
<ol style="list-style-type: decimal">
<li>The IP address from which you access the website;</li>
@@ -227,7 +227,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/project-info.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/project-info.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/project-info.html (original)
+++ archiva/site-content/redback/project-info.html Wed Apr 8 11:24:28 2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Project Information</title>
+ <title>Apache Redback – Project Information</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -206,10 +206,10 @@
<div id="bodyColumn" >
<div class="section">
-<h2>Project Information<a name="Project_Information"></a></h2>
+<h2><a name="Project_Information"></a>Project Information</h2>
<p>This document provides an overview of the various documents and links that
are part of this project's general information. All of this content is
automatically generated by <a class="externalLink"
href="http://maven.apache.org";>Maven</a> on behalf of the project.</p>
<div class="section">
-<h3>Overview<a name="Overview"></a></h3>
+<h3><a name="Overview"></a>Overview</h3>
<table border="0" class="table table-striped">
<tr class="a">
<th>Document</th>
@@ -240,7 +240,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/rbac/introduction.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/rbac/introduction.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/rbac/introduction.html (original)
+++ archiva/site-content/redback/rbac/introduction.html Wed Apr 8 11:24:28 2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - An Introduction to Role Based Access</title>
+ <title>Apache Redback – An Introduction to Role Based Access</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
<link rel="stylesheet" href="../css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -206,39 +206,39 @@
<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/mini/guide
-apt-format.html --><div class="section">
-<h2>An Introduction to Role Based Access<a
name="An_Introduction_to_Role_Based_Access"></a></h2>
+<h2><a name="An_Introduction_to_Role_Based_Access"></a>An Introduction to Role
Based Access</h2>
<p>This introduction provides background information on Role-Based Access
Control (RBAC), a technical means for controlling access to computer resources.
While still largely in the demonstration and prototype stages of development,
RBAC appears to be a promising method for controlling what information computer
users can utilize, the programs that they can run, and the modifications that
they can make. Only a few off-the-shelf systems that implement RBAC are
commercially available; however, organizations may want to start investigating
RBAC for future application in their multi-user systems. RBAC is appropriate
for consideration in systems that process unclassified but sensitive
information, as well as those that process classified information.</p></div>
<div class="section">
-<h2>What is Role-Based Access Control<a
name="What_is_Role-Based_Access_Control"></a></h2>
+<h2><a name="What_is_Role-Based_Access_Control"></a>What is Role-Based Access
Control</h2>
<p>Access is the ability to do something with a computer resource (e.g., use,
change, or view). Access control is the means by which the ability is
explicitly enabled or restricted in some way (usually through physical and
system-based controls). Computer- based access controls can prescribe not only
who or what process may have access to a specific system resource, but also the
type of access that is permitted. These controls may be implemented in the
computer system or in external devices.</p>
<p>With role-based access control, access decisions are based on the roles
that individual users have as part of an organization. Users take on assigned
roles (such as doctor, nurse, teller, manager). The process of defining roles
should be based on a thorough analysis of how an organization operates and
should include input from a wide spectrum of users in an organization.</p>
<p>Access rights are grouped by role name, and the use of resources is
restricted to individuals authorized to assume the associated role. For
example, within a hospital system the role of doctor can include operations to
perform diagnosis, prescribe medication, and order laboratory tests; and the
role of researcher can be limited to gathering anonymous clinical information
for studies.</p>
<p>The use of roles to control access can be an effective means for developing
and enforcing enterprise-specific security policies, and for streamlining the
security management process.</p></div>
<div class="section">
-<h2>Users and Roles<a name="Users_and_Roles"></a></h2>
+<h2><a name="Users_and_Roles"></a>Users and Roles</h2>
<p>Under the RBAC framework, users are granted membership into roles based on
their competencies and responsibilities in the organization. The operations
that a user is permitted to perform are based on the user's role. User
membership into roles can be revoked easily and new memberships established as
job assignments dictate. Role associations can be established when new
operations are instituted, and old operations can be deleted as organizational
functions change and evolve. This simplifies the administration and management
of privileges; roles can be updated without updating the privileges for every
user on an individual basis.</p>
<p>When a user is associated with a role:</p>
<p>the user can be given no more privilege than is necessary to perform the
job. This concept of least privilege requires identifying the user's job
functions, determining the minimum set of privileges required to perform that
function, and restricting the user to a domain with those privileges and
nothing more. In less precisely controlled systems, this is often difficult or
costly to achieve. Someone assigned to a job category may be allowed more
privileges than needed because is difficult to tailor access based on various
attributes or constraints. Since many of the responsibilities overlap between
job categories, maximum privilege for each job category could cause unlawful
access.</p></div>
<div class="section">
-<h2>Roles and Role Hierarchies<a name="Roles_and_Role_Hierarchies"></a></h2>
+<h2><a name="Roles_and_Role_Hierarchies"></a>Roles and Role Hierarchies</h2>
<p>Under RBAC, roles can have overlapping responsibilities and privileges;
that is, users belonging to different roles may need to perform common
operations. Some general operations may be performed by all employees. In this
situation, it would be inefficient and administratively cumbersome to specify
repeatedly these general operations for each role that gets created. Role
hierarchies can be established to provide for the natural structure of an
enterprise. A role hierarchy defines roles that have unique attributes and that
may contain other roles; that is, one role may implicitly include the
operations that are associated with another role.</p>
<p>In the healthcare situation, a role Specialist could contain the roles of
Doctor and Intern. This means that members of the role Specialist are
implicitly associated with the operations associated with the roles Doctor and
Intern without the administrator having to explicitly list the Doctor and
Intern operations. Moreover, the roles Cardiologist and Rheumatologist could
each contain the Specialist role.</p>
<p>Role hierarchies are a natural way of organizing roles to reflect
authority, responsibility, and competency:</p>
<p>the role in which the user is gaining membership is not mutually exclusive
with another role for which the user already possesses membership. These
operations and roles can be subject to organizational policies or constraints.
When operations overlap, hierarchies of roles can be established. Instead of
instituting costly auditing to monitor access, organizations can put
constraints on access through RBAC. For example, it may seem sufficient to
allow physicians to have access to all patient data records if their access is
monitored carefully. With RBAC, constraints can be placed on physician access
so that only those records that are associated with a particular physician can
be accessed.</p></div>
<div class="section">
-<h2>Roles and Operations<a name="Roles_and_Operations"></a></h2>
+<h2><a name="Roles_and_Operations"></a>Roles and Operations</h2>
<p>Organizations can establish the rules for the association of operations
with roles. For example, a healthcare provider may decide that the role of
clinician must be constrained to post only the results of certain tests but not
to distribute them where routing and human errors could violate a patient's
right to privacy. Operations can also be specified in a manner that can be used
in the demonstration and enforcement of laws or regulations. For example, a
pharmacist can be provided with operations to dispense, but not to prescribe,
medication.</p>
<p>An operation represents a unit of control that can be referenced by an
individual role, subject to regulatory constraints within the RBAC framework.
An operation can be used to capture complex security-relevant details or
constraints that cannot be determined by a simple mode of access.</p>
<p>For example, there are differences between the access needs of a teller and
an accounting supervisor in a bank. An enterprise defines a teller role as
being able to perform a savings deposit operation. This requires read and write
access to specific fields within a savings file. An enterprise may also define
an accounting supervisor role that is allowed to perform correction operations.
These operations require read and write access to the same fields of a savings
file as the teller. However, the accounting supervisor may not be allowed to
initiate deposits or withdrawals but only perform corrections after the fact.
Likewise, the teller is not allowed to perform any corrections once the
transaction has been completed. The difference between these two roles is the
operations that are executed by the different roles and the values that are
written to the transaction log file.</p>
<p>The RBAC framework provides administrators with the capability to regulate
who can perform what actions, when, from where, in what order, and in some
cases under what relational circumstances:</p>
<p>only those operations that need to be performed by members of a role are
granted to the role. Granting of user membership to roles can be limited. Some
roles can only be occupied by a certain number of employees at any given period
of time. The role of manager, for example, can be granted to only one employee
at a time. Although an employee other than the manager may act in that role,
only one person may assume the responsibilities of a manager at any given time.
A user can become a new member of a role as long as the number of members
allowed for the role is not exceeded.</p></div>
<div class="section">
-<h2>Advantages of RBAC<a name="Advantages_of_RBAC"></a></h2>
+<h2><a name="Advantages_of_RBAC"></a>Advantages of RBAC</h2>
<p>A properly-administered RBAC system enables users to carry out a broad
range of authorized operations, and provides great flexibility and breadth of
application. System administrators can control access at a level of abstraction
that is natural to the way that enterprises typically conduct business. This is
achieved by statically and dynamically regulating users' actions through the
establishment and definition of roles, role hierarchies, relationships, and
constraints. Thus, once an RBAC framework is established for an organization,
the username administrative actions are the granting and revoking of users into
and out of roles. This is in contrast to the more conventional and less
intuitive process of attempting to administer lower-level access control
mechanisms directly (e.g., access control lists [ACLs], capabilities, or type
enforcement entities) on an object-by-object basis.</p>
<p>Further, it is possible to associate the concept of an RBAC operation with
the concept of "method" in Object Technology. This association leads
to approaches where Object Technology can be used in applications and operating
systems to implement an RBAC operation.</p>
<p>For distributed systems, RBAC administrator responsibilities can be divided
among central and local protection domains; that is, central protection
policies can be defined at an enterprise level while leaving protection issues
that are of local concern at the organizational unit level. For example, within
a distributed healthcare system, operations that are associated with healthcare
providers may be centrally specified and pertain to all hospitals and clinics,
but the granting and revoking of memberships into specific roles may be
specified by administrators at local sites.</p></div>
<div class="section">
-<h2>Status of Current RBAC Activities<a
name="Status_of_Current_RBAC_Activities"></a></h2>
+<h2><a name="Status_of_Current_RBAC_Activities"></a>Status of Current RBAC
Activities</h2>
<p>Several organizations are experimenting with the inclusion of provisions
for RBAC in open consensus specifications. RBAC is an integral part of the
security models for Secure European System for Applications in a Multi-vendor
Environment (SESAME) distributed system and the database language SQL3. In
addition, the Object Management Group's (OMG) Common Object Request Broker
Architecture (CORBA) Security specification uses RBAC as an example of an
access control mechanism which can be used with the distributed Object
Technology defined by the OMG. (See reference below.)</p>
<p>CSL has been developing and defining RBAC and its applicability
cooperatively with industry, government, and academic partners. In conjunction
with Dr. Ravi Sandhu of George Mason University and Seta Corporation, CSL is
defining RBAC and its feasibility. We are working with Dr. Virgil Gligor and
his associates at the University of Maryland and with the National Security
Agency (NSA) to develop a formal reference model for RBAC to provide a safe,
effective, and consistent mechanism for access control. This effort is also
implementing RBAC on NSA's Synergy Platform, a secure platform based on the
Mach Operating System. CSL is also developing a demonstration of RBAC use in
healthcare. The access policy used in this demonstration is based on a draft
consensus policy for patient record access developed in the United Kingdom. In
conjunction with the Internal Revenue Service (IRS), CSL is defining roles and
operations suitable for the IRS environment. In conjunction with the Veterans Ad
ministration (VA), CSL is studying the applicability of RBAC to VA systems.</p>
<p>Based on current research and experience, RBAC appears to fit well into the
widely varying security policies of industry and government organizations.</p>
@@ -246,7 +246,7 @@
<p>http://waltz.ncsl.nist.gov/rbac/</p>
<p>or contact David Ferraiolo, [email protected], (301) 975-3046.</p></div>
<div class="section">
-<h2>References<a name="References"></a></h2>
+<h2><a name="References"></a>References</h2>
<p>Department of Defense, "Trusted Computer Security Evaluation
Criteria," DoD 5200.28-STD, 1985.</p>
<p>David F. Ferraiolo and D. Richard Kuhn, "Role-Based Access
Controls," Proceedings of the 15th NIST-NSA National Computer Security
Conference, Baltimore, Maryland, October 13-16, 1992.</p>
<p>David F. Ferraiolo, Dennis M. Gilbert, and Nickilyn Lynch, "An
Examination of Federal and Commercial Access Control Policy Needs,"
Proceedings of the 16th NIST-NSA National Computer Security Conference,
Baltimore, Maryland, September 20-23, 1993.</p>
@@ -271,7 +271,7 @@
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
Modified: archiva/site-content/redback/rbac/role-management.html
URL:
http://svn.apache.org/viewvc/archiva/site-content/redback/rbac/role-management.html?rev=1672063&r1=1672062&r2=1672063&view=diff
==============================================================================
--- archiva/site-content/redback/rbac/role-management.html (original)
+++ archiva/site-content/redback/rbac/role-management.html Wed Apr 8 11:24:28
2015
@@ -7,9 +7,9 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20140523" />
+ <meta name="Date-Revision-yyyymmdd" content="20150408" />
<meta http-equiv="Content-Language" content="en" />
- <title>Apache Redback - Redback Role Management</title>
+ <title>Apache Redback – Redback Role Management</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
<link rel="stylesheet" href="../css/print.css" media="print" />
@@ -180,7 +180,7 @@
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2014-05-23
+ <li id="publishDate">Last Published: 2015-04-08
<span class="divider">|</span>
</li>
<li class="">
@@ -206,10 +206,10 @@
<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/mini/guide
-apt-format.html --><div class="section">
-<h2>Role Management<a name="Role_Management"></a></h2>
+<h2><a name="Role_Management"></a>Role Management</h2>
<p>Managing roles in an application with Redback is governed through an
implementation of the Role Manager, an interface defined in the
redback-rbac-role-manager artifact that encapsulates most of the most comment
role related activities. User assignment of roles, creating and removing of
roles based on templates (more on this later), and simple role existence
activities. </p>
<div class="section">
-<h3>Role Specification<a name="Role_Specification"></a></h3>
+<h3><a name="Role_Specification"></a>Role Specification</h3>
<p>Roles are loaded by the Default implementation of the role manager from a
series of resources that are discovered in your classpath. The root of these
files is searched for as:</p>
<div class="source">
<pre>
@@ -222,7 +222,7 @@
</pre></div>
<p>Each of these files follows the same model, the one specified by <i>point
to xsd generated by modello</i>.</p>
<div class="section">
-<h4>Basic Format<a name="Basic_Format"></a></h4>
+<h4><a name="Basic_Format"></a>Basic Format</h4>
<div class="source">
<pre>
<redback-role-model>
@@ -270,22 +270,22 @@
</redback-role-model>
</pre></div></div>
<div class="section">
-<h4>Resources<a name="Resources"></a></h4>
+<h4><a name="Resources"></a>Resources</h4>
<p>Resources are the entities in role based access control that roles provide
access to through the binding of the resource with an operation in the form of
a permission. In the example above, 'cornflakes' are the resource that are in
play.</p></div>
<div class="section">
-<h4>Operations<a name="Operations"></a></h4>
+<h4><a name="Operations"></a>Operations</h4>
<p>Operations are conceptually actions that can be performed, somewhat akin to
verbs in the english language. 'Eat' in the example above is and action that
can be performed on any given resource.</p></div>
<div class="section">
-<h4>Roles<a name="Roles"></a></h4>
+<h4><a name="Roles"></a>Roles</h4>
<p>Roles are assignable entities that grant permissions to their assignies. In
this example, a user that has the can-eat-cornflakes role assigned can...eat
cornflakes.</p></div>
<div class="section">
-<h4>Permissions<a name="Permissions"></a></h4>
+<h4><a name="Permissions"></a>Permissions</h4>
<p>Permissions are the component of a role and role template that bind an
operation and a resource together into a form that is useful for authorization.
In this simple example we have the 'eat' operation being paired with the
'cornflake' resource which effectively allows assignees to eat thier
cornflakes.</p></div>
<div class="section">
-<h4>Templates<a name="Templates"></a></h4>
+<h4><a name="Templates"></a>Templates</h4>
<p>Templates address the fundamental issue in role based access control
systems regarding resources that may not exist at the time of role
specification. For example it would be virtually impossible to specific all
manner of possible foods you might encounter in life at application creation.
The 'eater-template' above addresses this. If you are exposed to 'tirimisu',
that would be created as a resource at runtime and then the eater-template
would be run with the tirimisu as its target resource (note the
${resource})</p></div></div>
<div class="section">
-<h3>Role Inheritance<a name="Role_Inheritance"></a></h3>
+<h3><a name="Role_Inheritance"></a>Role Inheritance</h3>
<p>Roles and Role templates would be woefully boring and tedious to work with
if there was not some concept of inheritence. Inhertiance is also added through
the model above.</p>
<div class="source">
<pre>
@@ -371,7 +371,7 @@ META-INF/redback/redback-core.xml
<p>With this example we have added another resource and operation, which can
be combined to allow a user to drink milk. We also added a new role called
'bowl-drinker' which has no additional permissions but illustrates the
childRole concept, that someone with this role effectively has the two child
roles, which when combined would all someone to eat their cornflakes in the
morning, and then drink the milk.</p>
<p>Also added to this example is the can-drink-milk role to the
eater-template, which would allow the user to automatically drink milk during
any meal that might be created during runtime.</p>
<div class="section">
-<h4>Parent Roles<a name="Parent_Roles"></a></h4>
+<h4><a name="Parent_Roles"></a>Parent Roles</h4>
<p>Since roles can be loaded up from different redback.xml files, it is
possible to reference roles in the redback-core.xml file and have them add a
child relationship to your role, and example of this is in play with continuum
and archiva both. Each of these applications define an extension of the System
Administrator role that is created in the redback-xwork-integration artifact
(where is the redback-core.xml is). These extensions would simply add:</p>
<div class="source">
<pre>
@@ -384,11 +384,11 @@ META-INF/redback/redback-core.xml
</pre></div>
<p>Then at role creation the role manager would know to have the System
Administrator role create a child role relationship with the corresponding
child role.</p></div>
<div class="section">
-<h4>Child and Parent Templates<a name="Child_and_Parent_Templates"></a></h4>
+<h4><a name="Child_and_Parent_Templates"></a>Child and Parent Templates</h4>
<p>Templates can also have child and parent relationships that are all
established during runtime. </p>
<p>NOTE: Roles can not declare childTemplate or parentTemplate relationships
since roles are created at startup time. One way around this restriction is to
add an aggregator role.</p></div>
<div class="section">
-<h4>Aggregator Roles<a name="Aggregator_Roles"></a></h4>
+<h4><a name="Aggregator_Roles"></a>Aggregator Roles</h4>
<p>One very useful role pattern to keep track off is an aggregator role. In
this case you would have the following example:</p>
<div class="source">
<pre>
@@ -430,7 +430,7 @@ META-INF/redback/redback-core.xml
<footer>
<div class="container">
<div class="row">
- <p >Copyright ©
2006–2014
+ <p >Copyright ©
2006–2015
<a href="http://www.apache.org/";>The Apache Software
Foundation</a>.
All rights reserved.
