Artifact repository user and role management
| Description | Nexus Roles | Users | |
|---|---|---|---|
| Admin users | Nexis Administrator Role | only a few selected super users | |
| Deployment users | Nexus Deployment Role and Repo: All Repositories (Full Control) | CI-servers | |
| Read-only users | Roles: one per project/company | one user per environment to be able to fetch artifacts when installing services. |
TODO: Stig will add link to page describing how to configure Jenkins CI server to support mvn release.
More fine-grained control can be added when needed. I.e. deployment users with read/write access only to selected repositories or read-only users which only can download from a few repositories.
Changes
- Set new admin password
- Disable the Anonymous user
- Set new password for deployment role
- Create new Repository target privilege 3rd party repo.
- Create new hosted repositories: project1-releases and project1-snapshots
- Create new Repository target privilege for each of these.
- Create new role with only read and view privileges
- read and view on both repositories
- read and view on thirdparty
- Artifact download
- UI: Search
- UI: Base UI privileges
- UI: Repository browser
- Create new read only user and give this user this role.
http://books.sonatype.com/nexus-book/reference/security-privileges.html