User Token vs CI token
Nexus Repository Pro uses tokens to authenticate users, tools, and automation workflows.
This topic explains the difference between User Tokens and CI tokens.
User Token
A User Token represents an individual user identity.
Use a User Token when:
- Running builds locally.
- Publishing artefacts manually.
- Accessing repositories from external tools on your workstation.
Characteristics:
- Tied to a specific user.
- Intended for development use.
- Generated from the Nexus UI.
CI token
A CI token represents a system identity.
Use a CI token when:
- Running CI/CD pipelines.
- Automating builds and deployments.
- Integrating Nexus with automation systems.
Characteristics:
- Not tied to a specific user.
- Designed for automation.
- More secure for pipeline usage.
Comparison
| Feature | User Token | CI token |
|---|---|---|
| Intended for | Individual users | Automation systems |
| Local development | Supported | Not recommended |
| CI/CD pipelines | Not recommended | Recommended |
| Linked to user account | Yes | No |
| Automation use | No | Yes |
