Maven Authentication

For authenticating via Maven, you need to have similar configuration in your settings.xml: 

<servers>
    <server>
        <id>repository-name-used-in-the-pom-to-refer-to-artifactory</id>
        <username>myUsername</username>
        <password>myPassword</password>
    </server>
</servers>

Repository and Path Permissions

Since version 1.2.1 of Artifactory, a new improved security model is used. The new model allows for setting permissions on targets that are a combination of a repository and a path prefix inside a repository.

The following permission-targets samples should make this concept clearer:

<repo>:<path> Description
lib-releases:org/apache refers to any artifact deployed under the "org/apache" path (including sub paths) inside the "lib-releases" repository
ANY:org/apache refers to any artifact deployed under the "org/apache" path (including sub paths) inside any repository
plugin-snapshots:ANY refers to any artifact deployed under any path inside the "plugin-snapshots" repository
ANY:ANY refers to any artifact deployed under any path inside any repository (this is useful for allowing global read permission for authenticated users, where anonymous download is not enabled)

The roles of admins, deployers and readers are still applicable for this new type of permission-targets.

The admin role is fully functional for one is an admin of.

For each permission-target you can assign users to 3 types of roles:

  1. Deployers - can deploy/remove (undeploy) artifacts.
  2. Viewers - can download artifacts (simple browsing is still enabled for anyone), unless a repository has the <anonDownloadsAllowed> flag set to true (the default), then anyone can download regardless of whether or not he is a viewer.
  3. Admins - can set permissions to other users inside the permission-target.

Global Admins

A defined user can either be a simple user or an "admin" user (similar to a root user). When a user is defined as an admin he automatically has all 3 roles for any repository or path.