Skip to main content
Connect Sonatype Nexus Repository so CloudThinker can check repository health, storage usage, task results, and component versions. The connection uses a username and password, or a Nexus user token, and only reads data.

Prerequisites

  • An existing self-hosted Nexus Repository 3 installation. This guide was verified with Community 3.96.5-05; Nexus Repository Cloud compatibility is unverified. For installation, follow Sonatype’s guide.
  • An HTTPS path from CloudThinker to Nexus. For CloudThinker Cloud, follow Reaching private services. On a self-hosted deployment of CloudThinker, allow access from your CloudThinker deployment.
  • A Nexus administrator who can create a dedicated user and assign roles.
  • The Admin role in your CloudThinker workspace. See Roles.

Setup

1

Create a role for CloudThinker

Ask your Nexus administrator to open Settings → Security → Roles → Create Role and select Nexus role. Enter a Role ID and Role Name, such as cloudthinker-reader.Under Privileges, choose Edit Privileges, select the privileges in Required permissions, and click Confirm, then Save. Leave Contained Roles empty. See Sonatype’s role instructions.
2

Create a dedicated local user

In Nexus, open Settings → Security → Users, select the Local source, and click Create user. Enter an ID, password, first and last name, and email. Set Status to Active and assign only the role you created.Save the user and keep its ID and password securely. The ID is the username you enter in CloudThinker. See Sonatype’s user instructions.
3

Add the connection in CloudThinker

Open More → Workspace settings → Connections, stay on Builtin Connections, and select Sonatype Nexus Repository. Click Connect and fill in the four fields below, then click Connect in the dialog.Success state: the connection shows a Connected status and reports how many repositories the user sees. This test checks repository access; run the verify prompt below to check storage, tasks, and system checks too.
If Nexus is missing from Builtin Connections, contact CloudThinker to confirm availability.

Connection details

Use your repository address, not the my.sonatype.com portal. CloudThinker refuses redirects, so include /nexus only if your installation uses that path. For a self-signed certificate, Skip SSL verification (self-signed) keeps traffic encrypted but cannot verify the server’s identity. Prefer a trusted certificate and verification; a publicly trusted HTTPS address needs no skip option. For a private certificate authority, contact CloudThinker. User tokens require a licensed Nexus entitlement. If your administrator already supplies a Nexus user token, enter its separate name code and passcode in the matching fields. Otherwise, use the local-user credentials above.

Required permissions

Assign these Nexus privileges for the checks you need: Replace repository wildcards with the formats and repositories CloudThinker should assess. On Nexus 3.57–3.75, search additionally requires repository-view read, which also allows downloads. From 3.76, browse plus search permission is sufficient; do not add download access by default.
Use a dedicated account, not an administrator. Privileges add together across roles: a narrow role cannot remove access granted by another role.

Agent capabilities

Repository and component results follow the user’s access. Lists are bounded; an incomplete search is not a full inventory. Missing size or download time means Nexus did not report it. Agents cannot change repositories, blob stores, cleanup policies, or tasks, run tasks, or delete components. Make those changes in Nexus. This connection does not provide vulnerability intelligence or upgrade recommendations; Sonatype Guide is a separate service.

Verify the connection

Expect real repository and blob store names, with task results and health checks. A failed section is unavailable data, not an empty list.

Example prompts

Troubleshooting

Recheck both credential fields. For a token, use its name code and matching passcode, rather than your username or the combined base64 value.
Ask your Nexus administrator to grant browse access to the intended repositories. Keep the repository scope narrow, then connect again.
Enter the final HTTPS address Nexus serves directly. Preserve its context path, and leave off the REST API suffix.
Confirm the address belongs to your Nexus Repository installation. Check the context path with its administrator. The Sonatype account portal is not a repository address.
Prefer a trusted certificate with Verify (recommended). Use the skip option only after accepting the identity-verification trade-off explained above.
Check which section failed and grant its permission from the table above. Connected confirms repository access, not every investigation permission. Retry the investigation after the role changes.
Enter the installation’s HTTPS address. For connection timeouts, confirm CloudThinker can reach that address through your firewall; browser access from your laptop alone is insufficient.

Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
  • Keep the Nexus account limited to the repositories and checks you need, even though this connection exposes no changes.
  • Keep certificate verification on and restrict network access to the sources that need Nexus.

Connections overview

Understand connection status, access, and credential rotation.

Jenkins

Investigate the builds that publish your components.