Setting up your first profile
Run the interactive wizard
y to configure a product, n to skip it.Auth types
cops supports two auth types per product. Choose the one that matches how your Atlassian Data Center instance is configured.Bearer token (default)
Bearer token (default)
Sends your Personal Access Token (PAT) in the
Authorization: Bearer <pat> header.This is the recommended auth type for Atlassian Data Center. Generate a PAT in your Atlassian product under Profile > Personal Access Tokens.Profile entry:Basic auth
Basic auth
Sends your username and token as a Base64-encoded
Authorization: Basic <base64(username:token)> header.Use basic auth when your instance does not support PATs or when you need to authenticate with a service account username and password.Profile entry:Profile structure
A profile is a named JSON object inconfig.json. Each product key (jira, confluence, bitbucket, bamboo) is optional — only configure the products you use.
Where profiles are stored
Profiles are persisted in a singleconfig.json file inside the cops config directory:
| Platform | Path |
|---|---|
| Linux / macOS | ~/.config/cops/config.json |
| Windows | %APPDATA%\cops\config.json |
On Linux and macOS, cops automatically sets the file permissions to
0600 (owner read/write only) every time it writes the config. On Windows, rely on standard user directory ACLs to restrict access.Managing profiles
List profiles
Switch the active profile
dc-staging profile until you switch again. Switching persists to config.json.
Delete a profile
Log out (unset current profile)
currentProfile pointer without deleting any profile. Subsequent commands will error until you run cops auth use <name> or cops auth login again.
