Sonatype Nexus Repository · Authentication Profile

Sonatype Nexus Repository Authentication

Authentication

Sonatype Nexus Repository secures its APIs with http, anonymous, and header across 5 declared security schemes, as derived from its OpenAPI definitions.

Artifact ManagementDevOpsDockerMavennpmPackage ManagementRepository ManagerSoftware Supply ChainRepositoryDeveloper ToolsArtifact RepositoryHelmNuGetOCIPyPISonatype
Methods: http, anonymous, header Schemes: 5 OAuth flows: API key in:

Security Schemes

basicAuth http
scheme: basic
userToken http
scheme: basic
remoteUserToken apiKey
· in: header ()
anonymous anonymous
saml-oidc-sso sso

Source

Authentication Profile

Raw ↑
generated: '2026-11-05'
method: searched
source:
- https://help.sonatype.com/en/authentication.html
- https://help.sonatype.com/en/user-tokens.html
- https://help.sonatype.com/en/user-tokens-api.html
- https://help.sonatype.com/en/authentication-via-remote-user-token.html
- https://help.sonatype.com/en/anonymous-access.html
- https://help.sonatype.com/en/realms.html
- openapi/_original/nexus-openapi.json
docs: https://help.sonatype.com/en/authentication.html
summary:
  types:
  - http
  - anonymous
  - header
  note: 'The published OpenAPI (3.97.2-02) declares no securitySchemes; every operation documents 401/403 responses. Authentication
    is instance-level: HTTP Basic with a local, LDAP, SAML or Crowd realm user, or a user-token pair used in place of username/password;
    anonymous read access is configurable; Remote User Token (RUT) header auth via a reverse proxy. SCIM is explicitly not
    supported.'
schemes:
- name: basicAuth
  type: http
  scheme: basic
  description: HTTP Basic authentication with a Nexus Repository user account from an active realm (local, LDAP, SAML, Atlassian
    Crowd). Sonatype recommends a centralized provider such as LDAP or SSO.
  docs: https://help.sonatype.com/en/authentication.html
  sources:
  - https://help.sonatype.com/en/authentication.html
  - https://help.sonatype.com/en/realms.html
- name: userToken
  type: http
  scheme: basic
  description: 'User tokens: a two-part token (name code / pass code) generated per user and sent in place of the username
    and password, so build tools (e.g. Maven settings.xml) do not store reversible credentials. Admins can create, get metadata,
    list and delete tokens via /v1/security/users/{userId}/{realm}/user-token and /v1/security/user-tokens/tokens; optional
    expiration; "Require User Tokens for Repository Authentication" setting. Only available in licensed (Pro) entitlements.'
  docs: https://help.sonatype.com/en/user-tokens.html
  sources:
  - https://help.sonatype.com/en/user-tokens.html
  - https://help.sonatype.com/en/user-tokens-api.html
- name: remoteUserToken
  type: apiKey
  in: header
  description: 'Remote User Token (RUT) authentication: a reverse proxy (Apache HTTPD, nginx) in front of Nexus Repository
    authenticates the user (PKI, CAS, SSO) and passes the username in an HTTP header that Nexus Repository trusts as the identity.'
  docs: https://help.sonatype.com/en/authentication-via-remote-user-token.html
  sources:
  - https://help.sonatype.com/en/authentication-via-remote-user-token.html
- name: anonymous
  type: anonymous
  description: Unauthenticated users who access the UI or download components are treated as the configurable anonymous user
    profile (Settings > Security > Anonymous Access); can be disabled.
  docs: https://help.sonatype.com/en/anonymous-access.html
  sources:
  - https://help.sonatype.com/en/anonymous-access.html
- name: saml-oidc-sso
  type: sso
  description: SAML 2.0 / OIDC single sign-on for Pro, Pro+ and Enterprise editions (editions matrix); configured via /v1/security/saml
    and /v1/security/oauth2 operations in the contract. Nexus Repository Cloud integrates the identity provider through my.sonatype.com.
  docs: https://help.sonatype.com/en/nexus-repository-tiers-and-feature-availability.html
  sources:
  - https://help.sonatype.com/en/nexus-repository-tiers-and-feature-availability.html
  - openapi/nexus-security-management-saml-api-openapi.yml
  - openapi/nexus-security-oauth2-oidc-api-openapi.yml
not_supported:
  scim: '"Direct System for Cross-domain Identity Management (SCIM) is not supported." (https://help.sonatype.com/en/authentication.html)'

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/nexus-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.