You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@archiva.apache.org by ma...@apache.org on 2017/05/13 15:58:32 UTC
svn commit: r1795074 - in /archiva/site-content/docs/2.2.3:
adminguide/configuration-files.html adminguide/customising-security.html
adminguide/redback-runtime-configuration.html adminguide/repositories.html
css/site.css release-notes.html
Author: martin_s
Date: Sat May 13 15:58:31 2017
New Revision: 1795074
URL: http://svn.apache.org/viewvc?rev=1795074&view=rev
Log:
Apache Archiva Versionned docs for 2.2.3
Modified:
archiva/site-content/docs/2.2.3/adminguide/configuration-files.html
archiva/site-content/docs/2.2.3/adminguide/customising-security.html
archiva/site-content/docs/2.2.3/adminguide/redback-runtime-configuration.html
archiva/site-content/docs/2.2.3/adminguide/repositories.html
archiva/site-content/docs/2.2.3/css/site.css
archiva/site-content/docs/2.2.3/release-notes.html
Modified: archiva/site-content/docs/2.2.3/adminguide/configuration-files.html
URL: http://svn.apache.org/viewvc/archiva/site-content/docs/2.2.3/adminguide/configuration-files.html?rev=1795074&r1=1795073&r2=1795074&view=diff
==============================================================================
--- archiva/site-content/docs/2.2.3/adminguide/configuration-files.html (original)
+++ archiva/site-content/docs/2.2.3/adminguide/configuration-files.html Sat May 13 15:58:31 2017
@@ -341,7 +341,7 @@
<p>The following files compose the configuration for Archiva:</p>
<ul>
<li><tt>archiva.xml</tt> - this is the primary Archiva configuration file</li>
-<li><tt>security.properties</tt> - this configures the security as described in the <a href="./security.html"> security configuration documentation</a></li></ul>
+<li><tt>security.properties</tt> - This file, if it exists, is only read once to populate the Redback Runtime Configuration properties (see <a href="./redback-runtime-configuration.html#Runtime_Properties">Redback Runtime Configuration</a>, stored in <tt>archiva.xml</tt>. The file will be ignored after this.</li></ul>
<p>This section will focus on the <tt>archiva.xml</tt> file.</p>
<div class="section">
<h3><a name="The_Archiva_configuration_file"></a>The Archiva configuration file</h3>
Modified: archiva/site-content/docs/2.2.3/adminguide/customising-security.html
URL: http://svn.apache.org/viewvc/archiva/site-content/docs/2.2.3/adminguide/customising-security.html?rev=1795074&r1=1795073&r2=1795074&view=diff
==============================================================================
--- archiva/site-content/docs/2.2.3/adminguide/customising-security.html (original)
+++ archiva/site-content/docs/2.2.3/adminguide/customising-security.html Sat May 13 15:58:31 2017
@@ -360,35 +360,147 @@
<!-- 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><a name="Archiva_Security_Configuration"></a>Archiva Security Configuration</h2>
-<p>Security properties and password rules can be configured in the <tt>security.properties</tt> file, which by default is searched for in:</p>
-<ul>
-<li><tt>~/.m2/security.properties</tt></li>
-<li><tt>conf/security.properties</tt> in the Archiva installation</li></ul>
-<p>(In the above list, <tt>~</tt> is the home directory of the user who is running Archiva.)</p><!-- TODO: Link to plexus-redback documentation when available -->
-<p>Following are some of the properties you can modify. For a complete list, consult the default properties file in Redback's svn repo: <a class="externalLink" href="http://svn.apache.org/repos/asf/archiva/redback/redback-core/trunk/redback-configuration/src/main/resources/org/apache/archiva/redback/config-defaults.properties"> config-defaults.properties</a></p>
+<p>Security properties and password rules are configured now in the Redback Runtime Configuration properties (see <a href="./redback-runtime-configuration.html#Runtime_properties">Redback Runtime Configuration</a>).</p>
+<p>The Redback Runtime Configuration properties are stored in <tt>archiva.xml</tt>. The former <tt>security.properties</tt> file, if it exists, is only used once for populating the Runtime Configuration settings. After that, this file will be ignored.</p><!-- TODO: Link to plexus-redback documentation when available -->
+<p>These are the default properties. The file can be found in in Redback's svn repo: <a class="externalLink" href="http://svn.apache.org/repos/asf/archiva/redback/redback-core/trunk/redback-configuration/src/main/resources/org/apache/archiva/redback/config-defaults.properties"> config-defaults.properties</a></p>
<div class="source">
-<pre># Security Policies
-# -----------------
+<pre># 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.
+
+# --------------------------------------------------------------------
+# Application Configuration
+
+application.timestamp=EEE d MMM yyyy HH:mm:ss Z
+
+# --------------------------------------------------------------------
+# JDBC Setup
+
+#jdbc.driver.name=org.apache.derby.jdbc.EmbeddedDriver
+#jdbc.url=jdbc:derby:memory:users-tests;create=true
+
+jdbc.driver.name=org.hsqldb.jdbcDriver
+jdbc.url=jdbc:hsqldb:mem:redback-test
+
+jdbc.username=sa
+jdbc.password=
+
+# --------------------------------------------------------------------
+# Email Settings
+
+email.jndiSessionName=java:comp/env/mail/Session
+email.smtp.host=localhost
+email.smtp.port=25
+email.smtp.ssl.enabled=false
+email.smtp.tls.enabled=false
+email.smtp.username=
+email.smtp.password=
+
+#TODO: move description elsewhere, remove bad default
+# All emails sent by the system will be from the following address
+#email.from.address=${user.name}@localhost
+# All emails sent by the system will be from the following user name (used in conjunction with address)
+#email.from.name=Unconfigured Username
+
+# If all email addresses (from new user registration) require an account validation email.
+email.validation.required=true
+# Timeout (in minutes) for the key generated for an email validation to remain valid.
+# 2880 minutes = 48 hours
+email.validation.timeout=2880
+# The subject line for the email message.
+email.validation.subject=Welcome
+
+#TODO: move description elsewhere, remove bad default
+# Get the Feedback to use for any outgoing emails.
+# NOTE: if 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:feedback@application.com"
+#email.feedback.path=/feedback.action
+
+#Set the application base URL. The default is to derive it from the HTTP request
+#application.url=http://myurl.mycompany.com
+
+# --------------------------------------------------------------------
+# Auto Login Settings
+
+security.rememberme.enabled=true
+# Timeout in days ( 365 days = 1 year )
+security.rememberme.timeout=365
+security.rememberme.path=/
+security.rememberme.domain=
+security.rememberme.secure=false
+
+# Single Sign On
+# Timeout in minutes
+security.signon.timeout=30
+
+# --------------------------------------------------------------------
+# Default Username Values
+redback.default.admin=admin
+redback.default.guest=guest
+
+# --------------------------------------------------------------------
+# Security Policies
+
#security.policy.password.encoder=
security.policy.password.previous.count=6
-security.policy.password.expiration.days=90
security.policy.password.expiration.enabled=true
-security.policy.allowed.login.attempt=3
+security.policy.password.expiration.days=90
+security.policy.password.expiration.notify.days=10
+security.policy.allowed.login.attempt=10
+# turn off the perclick enforcement of various security policies, slightly
+# more heavyweight since it will ensure that the User object on each click
+# is up to date
+security.policy.strict.enforcement.enabled=true
+security.policy.strict.force.password.change.enabled=true
+
+# --------------------------------------------------------------------
# Password Rules
-# --------------
security.policy.password.rule.alphanumeric.enabled=false
security.policy.password.rule.alphacount.enabled=true
security.policy.password.rule.alphacount.minimum=1
security.policy.password.rule.characterlength.enabled=true
security.policy.password.rule.characterlength.minimum=1
-security.policy.password.rule.characterlength.maximum=8
+security.policy.password.rule.characterlength.maximum=24
security.policy.password.rule.musthave.enabled=true
security.policy.password.rule.numericalcount.enabled=true
security.policy.password.rule.numericalcount.minimum=1
security.policy.password.rule.reuse.enabled=true
security.policy.password.rule.nowhitespace.enabled=true
+# --------------------------------------------------------------------
+# ldap settings
+#
+ldap.bind.authenticator.enabled=false
+
+# ldap options for configuration via properties file
+#ldap.config.hostname=
+#ldap.config.port=
+#ldap.config.base.dn=
+#ldap.config.context.factory=
+#ldap.config.bind.dn=
+#ldap.config.password=
+#ldap.config.authentication.method=
+
+# config parameter for the ConfigurableUserManager
+user.manager.impl=jdo
+
+
+# REST security settings
+
# Cross Site Request Forgery (CSRF) Prevention
# --------------------------------------------
# Enable/Disable CSRF filtering.
@@ -404,7 +516,8 @@ rest.csrffilter.absentorigin.deny=true
# Enable/Disable the token validation only.
# If true, the validation of the CSRF tokens will be disabled.
# Possible values: true, false
-rest.csrffilter.disableTokenValidation=false</pre></div>
+rest.csrffilter.disableTokenValidation=false
+</pre></div>
<p><b>Note:</b> If installed standalone, Archiva's list of configuration files is <i>itself</i> configurable, and can be found in: <tt>apps/archiva/WEB-INF/applicationContext.xml</tt></p>
<p>Values from sources</p>
<div class="source">
Modified: archiva/site-content/docs/2.2.3/adminguide/redback-runtime-configuration.html
URL: http://svn.apache.org/viewvc/archiva/site-content/docs/2.2.3/adminguide/redback-runtime-configuration.html?rev=1795074&r1=1795073&r2=1795074&view=diff
==============================================================================
--- archiva/site-content/docs/2.2.3/adminguide/redback-runtime-configuration.html (original)
+++ archiva/site-content/docs/2.2.3/adminguide/redback-runtime-configuration.html Sat May 13 15:58:31 2017
@@ -441,7 +441,7 @@
<li><a href="#Users_Cache">Users Cache</a></li></ul></li></ul>
<div class="section">
<h3><a name="Apache_Redback_User_ManagerRbacManager_Implementations"></a>Apache Redback User Manager/RbacManager Implementations</h3>
-<p>Since 1.4-M4, you can choose to switch dynamically</p>
+<p>You can choose to switch dynamically</p>
<ul>
<li>User Manager Implementations (from Database and/or LDAP).</li>
<li>RbacManager Implementations (from Database and/or LDAP): to manage if roles management comes from Database and/or LDAP.</li></ul><img src="../images/redback-runtime-conf-general.png" alt="" /></div>
@@ -451,7 +451,7 @@
<p>You can test your ldap configuration too.</p><img src="../images/ldap-configuration.png" alt="" /></div>
<div class="section">
<h3><a name="LDAP_Group-Roles_mapping"></a>LDAP Group-Roles mapping</h3>
-<p>Since 1.4-M4, you can map dynamically LDAP Group to Archiva Roles</p><img src="../images/ldap-group-roles-mapping.png" alt="" /></div>
+<p>You can map dynamically LDAP Group to Archiva Roles</p><img src="../images/ldap-group-roles-mapping.png" alt="" /></div>
<div class="section">
<h3><a name="Runtime_properties"></a>Runtime properties</h3>
<p>You can now too modify some Redback configuration properties. You have a help button which explains to you what the property is doing.</p><img src="../images/redback-properties.png" alt="" /></div>
Modified: archiva/site-content/docs/2.2.3/adminguide/repositories.html
URL: http://svn.apache.org/viewvc/archiva/site-content/docs/2.2.3/adminguide/repositories.html?rev=1795074&r1=1795073&r2=1795074&view=diff
==============================================================================
--- archiva/site-content/docs/2.2.3/adminguide/repositories.html (original)
+++ archiva/site-content/docs/2.2.3/adminguide/repositories.html Sat May 13 15:58:31 2017
@@ -437,22 +437,55 @@ Olivier Lamy" />
<h3><a name="Managed_Repository"></a>Managed Repository</h3>
<p>A managed repository is a repository which resides locally to the server where Archiva is running. It could serve as a proxy repository, an internal deployment repository or a local mirror repository.</p>
<p>Managed repository fields:</p>
-<ul>
-<li><b>identifier</b> - the id of the repository. This must be unique.</li>
-<li><b>name</b> - the name of the repository.</li>
-<li><b>directory</b> - the location of the repository. If the path specified does not exist, Archiva will create the missing directories.</li>
-<li><b>index directory</b> - the location of the index files generated by Archiva. If no location is specified, then the index directory (named <tt>.indexer</tt>) will be created at the root of the repository directory. This directory contains the packaged/bundled index which is consumed by different consumers of the index such as M2Eclipse.</li>
-<li><b>type</b> - the repository layout (maven 2 or maven 1)</li>
-<li><b>cron</b> - the <a class="externalLink" href="http://quartz-scheduler.org/api/2.1.5/org/quartz/CronTrigger.html">cron schedule</a> when repository scanning will be executed.</li>
-<li><b>repository purge by days older</b> - the first option for repository purge. Archiva will check how old the artifact is and if it is older than the set number of days in this field, then the artifact will be deleted respecting the retention count of course. In order to disable the purge by number of days old and set Archiva to purge by retention count, just set the repository purge field to 0. The maximum number of days which can be set here is 1000. See the Repository Purge section below for more details.</li></ul><!-- above was:the retention count (see #7) of course no idea what is was linkeed to -->
-<ul>
-<li><b>repository purge by retention count</b> - the second option for repository purge. When running the repository purge, Archiva will retain only the number of artifacts set for this field for a specific snapshot version. See the Repository Purge section below for more details.</li>
-<li><b>releases included</b> - specifies whether there are released artifacts in the repository.</li>
-<li><b>block re-deployment of released artifacts</b> - specifies whether released artifacts that are already existing in the repository can be overwritten. Note that this only take effects for non-snapshot deployments.</li>
-<li><b>snapshots included</b> - specifies whether there are snapshot artifacts in the repository.</li>
-<li><b>scannable</b> - specifies whether the repository can be scanned, meaning it is a local repository which can be indexed, browsed, purged, etc.</li>
-<li><b>delete released snapshots</b> - specifies whether to remove those snapshot artifacts which already has release versions of it in the repository during repository purge.</li>
-<li><b> Skip Packed Index creation </b> - avoid creation of compressed index for IDE usage.</li></ul><img src="../images/managed-repositories.png" alt="Managed Repositories" />
+<table border="1" class="table table-striped">
+<tr class="a">
+<td align="left"><b>Id</b></td>
+<td align="left">The identifier of the repository. This must be unique.</td></tr>
+<tr class="b">
+<td align="left"><b>Name</b></td>
+<td align="left">The name of the repository. This is the display name.</td></tr>
+<tr class="a">
+<td align="left"><b>Directory</b></td>
+<td align="left">The location of the repository. If the path specified does not exist, Archiva will create the missing directories.</td></tr>
+<tr class="b">
+<td align="left"><b>Index Directory</b></td>
+<td align="left">The location of the index files generated by Archiva. If no location is specified, then the index directory (named <tt>.indexer</tt>) will be created at the root of the repository directory. This directory contains the packaged/bundled index which is consumed by different consumers of the index such as M2Eclipse.</td></tr>
+<tr class="a">
+<td align="left"><b>Type</b></td>
+<td align="left">The repository layout (maven 2 or maven 1)</td></tr>
+<tr class="b">
+<td align="left"><b>Cron Expression</b></td>
+<td align="left">The <a class="externalLink" href="http://www.quartz-scheduler.org/documentation/quartz-2.x/tutorials/crontrigger.html">cron schedule</a> when repository scanning will be executed.</td></tr>
+<tr class="a">
+<td align="left"><b>Days Older</b></td>
+<td align="left">The first option for repository purge. Archiva will check how old the artifact is and if it is older than the set number of days in this field, then the artifact will be deleted respecting the retention count of course. In order to disable the purge by number of days old and set Archiva to purge by retention count, just set the repository purge field to 0. The maximum number of days which can be set here is 1000. See the Repository Purge section below for more details.</td></tr>
+<tr class="b">
+<td align="left"><b>Retention Count</b></td>
+<td align="left">The second option for repository purge. When running the repository purge, Archiva will retain only the number of artifacts set for this field for a specific snapshot version. See the Repository Purge section below for more details.</td></tr>
+<tr class="a">
+<td align="left"><b>Description</b></td>
+<td align="left">Additional information about the repository.</td></tr>
+<tr class="b">
+<td align="left"><b>Releases</b></td>
+<td align="left">Specifies whether there are released artifacts in the repository.</td></tr>
+<tr class="a">
+<td align="left"><b>Snapshots</b></td>
+<td align="left">Specifies whether there are snapshot artifacts in the repository.</td></tr>
+<tr class="b">
+<td align="left"><b>Block Redeployments</b></td>
+<td align="left">Specifies whether released artifacts that are already existing in the repository can be overwritten. Note that this only take effects for non-snapshot deployments.</td></tr>
+<tr class="a">
+<td align="left"><b>Scanned</b></td>
+<td align="left">Specifies whether the repository can be scanned, meaning it is a local repository which should be indexed, purged, etc.</td></tr>
+<tr class="b">
+<td align="left"><b>Delete Released Snapshots</b></td>
+<td align="left">Specifies whether to remove those snapshot artifacts which already has release versions of it in the repository during repository purge.</td></tr>
+<tr class="a">
+<td align="left"><b>Staging Repository</b></td>
+<td align="left">Automatic creation of a stage repository for this local repository.</td></tr>
+<tr class="b">
+<td align="left"><b> Skip Packed Index Creation</b></td>
+<td align="left">Avoid creation of compressed index for IDE usage.</td></tr></table><img src="../images/managed-repositories.png" alt="Managed Repositories" />
<p>Each repository has its own http(s)/webdav url. This allows the user to browse and access the repository via http(s)/webdav. The url has the following format:</p>
<div class="source">
<pre>http://[URL TO ARCHIVA]/repository/[REPOSITORY ID] (e.g. http://localhost:8080/repository/releases).</pre></div>
@@ -461,22 +494,61 @@ Olivier Lamy" />
<h3><a name="Remote_Repository"></a>Remote Repository</h3>
<p>A remote repository is a repository which resides remotely. These repositories are usually the proxied repositories. See Proxy Connectors on how to proxy a repository.</p>
<p>Remote repository fields:</p>
-<ul>
-<li><b>identifier</b> - the id of the remote repository.</li>
-<li><b>name</b> - the name of the remote repository.</li>
-<li><b>url</b> - the url of the remote repository. It is also possible to use a 'file://' url to proxy a local repository. Be careful that if this local repository is a managed repository of archiva which has some proxies connectors, those ones won't be triggered.</li>
-<li><b>username</b> - the username (if authentication is needed) to be used to access the repository.</li>
-<li><b>password</b> - the password (if authentication is needed) to be used to access the repository.</li>
-<li><b>type</b> - the layout (maven 2 or maven 1) of the remote repository.</li>
-<li><b>Activate download remote index</b> - to activate downloading remote index to add available remote artifacts in search queries.</li>
-<li><b>Remote index url, can be relative to url</b> - path of the remote index directory.</li>
-<li><b>Cron expression</b> - cron expression for downloading remote index (default weekly on sunday)</li>
-<li><b>Directory index storage</b> - path to store index directory, default will be ${appserver.base}/data/remotes/${repositoryId}/.indexer</li>
-<li><b>Download Remote Index Timeout in seconds</b> - read time out for downloading remote index files (default 300)</li>
-<li><b>Network Proxy to Use for download Remote Index</b> - proxy to use for downloading remote index files.</li>
-<li><b>Download Remote Index on Startup</b> - will download remote index on Archiva startup.</li>
-<li><b>Additionnal url parameters</b> - key/value pairs to add to url when querying remote repository.</li>
-<li><b>Additionnal Http Headers</b> - key/value pairs to add as http headers when querying remote repository.</li></ul><img src="../images/remote-repositories.png" alt="Remote Repositories" />
+<table border="1" class="table table-striped">
+<tr class="a">
+<td align="left"><b>Id</b></td>
+<td align="left">The identifier of the remote repository.</td></tr>
+<tr class="b">
+<td align="left"><b>Name</b></td>
+<td align="left">The name of the remote repository.</td></tr>
+<tr class="a">
+<td align="left"><b>Url</b></td>
+<td align="left">The url of the remote repository. It is also possible to use a 'file://' url to proxy a local repository. Be careful that if this local repository is a managed repository of archiva which has some proxies connectors, those ones won't be triggered.</td></tr>
+<tr class="b">
+<td align="left"><b>Username</b></td>
+<td align="left">The username (if authentication is needed) to be used to access the repository.</td></tr>
+<tr class="a">
+<td align="left"><b>Password</b></td>
+<td align="left">The password (if authentication is needed) to be used to access the repository.</td></tr>
+<tr class="b">
+<td align="left"><b>Download Timeout</b></td>
+<td align="left">The time in seconds after which a download from the remote repository is stopped.</td></tr>
+<tr class="a">
+<td align="left"><b>Type</b></td>
+<td align="left">The layout (maven 2 or maven 1) of the remote repository.</td></tr>
+<tr class="b">
+<td align="left"><b>Download Remote Index</b></td>
+<td align="left">To activate downloading remote index to add available remote artifacts in search queries.</td></tr>
+<tr class="a">
+<td align="left"><b>Remote Index Url</b></td>
+<td align="left">Can be relative to Url - path of the remote index directory.</td></tr>
+<tr class="b">
+<td align="left"><b>Cron expression</b></td>
+<td align="left">Cron expression for downloading remote index (default weekly on sunday)</td></tr>
+<tr class="a">
+<td align="left"><b>Index Directory</b></td>
+<td align="left">Path to store index directory, default will be ${appserver.base}/data/remotes/${repositoryId}/.indexer</td></tr>
+<tr class="b">
+<td align="left"><b>Download Remote Index Timeout</b></td>
+<td align="left">Time in seconds, after which download of remote index files will be stopped (default 300).</td></tr>
+<tr class="a">
+<td align="left"><b>Proxy for Remote Download Index</b></td>
+<td align="left">Proxy to use for downloading remote index files.</td></tr>
+<tr class="b">
+<td align="left"><b>Download Remote Index on Startup</b></td>
+<td align="left">If selected, the remote index will be downloaded on Archiva startup.</td></tr>
+<tr class="a">
+<td align="left"><b>Description</b></td>
+<td align="left">Can be used to store additional information about the repository.</td></tr>
+<tr class="b">
+<td align="left"><b>Connection Check Path</b></td>
+<td align="left">If set, the connection to the remote repository is checked by validating the existence of the given file / artifact. Some repositories do not allow to browse the base directory and the standard check may fail. The path is relative to the repository Url.</td></tr>
+<tr class="a">
+<td align="left"><b>Additionnal Url Parameters</b></td>
+<td align="left">Key/Value pairs to add to url when querying remote repository.</td></tr>
+<tr class="b">
+<td align="left"><b>Additionnal Http Headers</b></td>
+<td align="left">Key/Value pairs to add as http headers when querying remote repository.</td></tr></table><img src="../images/remote-repositories.png" alt="Remote Repositories" />
<p>You can also trigger an immediate download of remote index files.</p>
<div class="section">
<h4><a name="Maven_Index_from_Remote_repositories"></a>Maven Index from Remote repositories</h4>
Modified: archiva/site-content/docs/2.2.3/css/site.css
URL: http://svn.apache.org/viewvc/archiva/site-content/docs/2.2.3/css/site.css?rev=1795074&r1=1795073&r2=1795074&view=diff
==============================================================================
--- archiva/site-content/docs/2.2.3/css/site.css (original)
+++ archiva/site-content/docs/2.2.3/css/site.css Sat May 13 15:58:31 2017
@@ -70,6 +70,15 @@ pre.commandline {
color: gray;
}
+img {
+ border-style: solid ;
+ border-width: 1px;
+ border-color: #ddd;
+ padding: 5px;
+ margin-top: 10px;
+ border-radius: 5px;
+}
+
pre.commandline .input {
color: #55f;
}
Modified: archiva/site-content/docs/2.2.3/release-notes.html
URL: http://svn.apache.org/viewvc/archiva/site-content/docs/2.2.3/release-notes.html?rev=1795074&r1=1795073&r2=1795074&view=diff
==============================================================================
--- archiva/site-content/docs/2.2.3/release-notes.html (original)
+++ archiva/site-content/docs/2.2.3/release-notes.html Sat May 13 15:58:31 2017
@@ -351,8 +351,9 @@
<div class="section">
<h3><a name="Compatibility_Changes"></a>Compatibility Changes</h3>
<ul>
-<li>The REST services are now checking for the origin of the requests by analysing Origin and Referer header of the HTTP requests and adding an validation token to the Header. This prevents requests from malicious sites if they are open in the same browser. If you use the REST services from other clients you may change the behaviour with the new configuration properties for the redback security (rest.csrffilter.*, rest.baseUrl). For more information see <a href="./adminguide/customising-security.html">Archiva Security Configuration</a> and the <a href="/redback/integration/rest.html">Redback REST documentation </a></li>
-<li>Archiva uses redback for authentication and authorization in version 2.5</li></ul></div>
+<li>The REST services are now checking for the origin of the requests by analysing Origin and Referer header of the HTTP requests and adding an validation token to the Header. This prevents requests from malicious sites if they are open in the same browser. If you use the REST services from other clients you may change the behaviour with the new configuration properties for the redback security (<tt>rest.csrffilter.*</tt>, <tt>rest.baseUrl</tt>). For more information see <a href="./adminguide/customising-security.html">Archiva Security Configuration</a> and the <a href="/redback/integration/rest.html">Redback REST documentation </a>.
+<p><b>Note:</b> If your archiva installation is behind a reverse proxy or load balancer, it may be possible that the Archiva Web UI does not load after the upgrade. If this is the case you may access the WebUI via localhost or edit archiva.xml manually. In the "Redback Runtime Configuration" properties you have to enter the base URLs of your archiva installation to the <tt>rest.baseUrl</tt> field.</p></li>
+<li>Archiva uses redback for authentication and authorization in version 2.6</li></ul></div>
<div class="section">
<h3><a name="Release_Notes"></a>Release Notes</h3>
<p>The Archiva 2.2.3 features set can be seen in the <a href="./tour/index.html"> feature tour</a>.</p></div>