blob: dae3ca7348178ad22e78d8119f58382f1450d3bd (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
------
Understanding Apache Archiva Security Roles
------
~~ 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.
Understanding Apache Archiva Security Roles
Archiva uses the {{{http://archiva.apache.org/redback/} Redback}} security framework for managing repository security. When the server is first started,
you will be prompted to create an administration user. This user will be given permission to administer all aspects of the system (as well as
access to all of the repositories). This user can then be used to grant permissions to other users.
A guest user is also created by default, and given read access to the default repositories (<<<internal>>> and <<<snapshots>>>). Repositories with
guest user access can be accessed without the use of a username and password (or without being logged in to the web interface).
However, when new repositories are created, by default no permissions are assigned and only the administrators will have access until it is
explicitly granted.
Note that Redback has the concept of inferred roles, so the assignment of some roles will imply other roles (which will be displayed in the web interface).
* Repository Roles
Archiva contains the following roles for repository access:
* <Repository Observer>: users with this role can read from the given repository that the role is for (including access through the browse and search features of the
web interface)
* <Repository Manager>: users with this role can write to and administer the given repository that the role is for
* <Global Repository Observer>: users with this role can read from any repository (including access through the browse and search features of the
web interface)
* <Global Repository Manager>: users with this role can write to and administer any repository in the instance
* General Roles
Archiva also contains the following general roles for security of the instance:
* <System Administrator>: full access to all functionality in the system
* <User Administrator>: ability to create, edit, and grant roles to other users in the system
The guest and registered user roles do not affect repository access.
~~TODO: walkthrough screens
|
