opschain admin jsm-connections create
integrations:jira-service-management
Registers a JSM connection. Exactly one credential half is supplied:
--api-token-ref pins an existing secret-vault:// reference
(resolved at write time), or an inline API token / PAT rides
--api-token-env or --api-token-prompt (never the command line) and
the server vaults it under jsm-connections/<code>/credential and
pins the reference. Requires the integrations:jira-service-management
entitlement.
JSM_TOKEN=... opschain admin jsm-connections create limepoint-jsm \
--base-url https://limepoint.atlassian.net \
--auth-email support-bot@limepoint.example \
--project-keys SUP --api-token-env JSM_TOKEN
Created JSM connection limepoint-jsm for https://limepoint.atlassian.net (api_token_ref secret-vault://jsm-connections/limepoint-jsm/credential)
Flags
| Flag | Meaning |
|---|---|
--server <url> | Server base URL (default: the active context / OPSCHAIN_SERVER). |
--auth-token <token> | Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login). |
--display-name <name> | Human-readable connection name. |
--base-url <url> | The Atlassian cloud site or Jira Data Center base URL. |
--auth-email <email> | The Atlassian account email the API token belongs to; omit for a Data Center PAT sent as a bearer. |
--api-token-ref <ref> | A secret-vault:// reference to pin (mutually exclusive with the inline token flags). |
--api-token-env <name> | Environment variable holding the API token / PAT. |
--api-token-prompt | Prompt for the API token / PAT without echo. |
--project-keys <keys> | Project keys to scope the connection to, e.g. SUP,OPS (writes outside them refuse; empty: unscoped). |
--enabled | Whether the connection serves outbound writes (default true). |
See also
opschain docs cli/admin-jsm-connections-provision-webhook— the inbound half.