Brand Onboarding

Registers a brand with the PSV-IM Agent — its Capillary credentials and the allowed-brand pattern that makes the agent pick its tickets up. Both have to be right or the failure is invisible, so this page validates as a dry run first and only then writes.

Checking who you are…

1Brand identity

Why this matters
The agent resolves a ticket to a brand by Org ID, and finds the credentials to call Capillary with by Cluster URL. Brand is the string the allowed-brand pattern is matched against — it should read the way the ticket's Brand field reads, e.g. Indigo UAT, not an internal shorthand.
The key the agent looks a brand up by. Usually digits, but stored as free text.
The live customfield_11997 options, read from Jira — the same list the ticket form uses. Onboarding a name that is not a real Jira brand produces a pattern that can never match a ticket, so this is a closed list rather than free text.
Required to write. This server holds no admin token of its own, so only people trusted with one can onboard a brand. It is sent as a header for this request only — never stored, never logged, never saved in your browser.
Where this brand's credentials get used at runtime. Only the known Capillary clusters are accepted — the server rejects anything else.

2Capillary credentials

Why this matters
A brand that matches an active pattern but cannot authenticate makes the agent accept the ticket and then fail at the credential gate — which reads as a broken agent rather than an unfinished setup. The secret is write-only from this page: it is sent to the agent service and never read back, and this page has no way to reveal a stored one.
Masked here and stored masked. Never returned by this page.

3Allowed-brand pattern auto

Why this matters
The pattern is matched case-insensitively as a substring, pattern inside brand. indigo matches Indigo UAT; Indigo UAT does not match indigo. If it cannot match, the agent silently never picks the brand's tickets up — which is why the dry run refuses rather than writing a pattern that can never fire. This is filled in for you the moment you pick a brand, from the brand's first word — the same rule the agent service applies to a blank one. Overwrite it if the brand needs a narrower or wider match.
At least 3 characters — a shorter substring matches most brands in the estate.

4Neo login

Why this matters
The Capillary credentials above let the agent call the brand's APIs. This is the account it signs into the Neo CLI with to read the brand's rules and dataflows — which is how it actually investigates a ticket. Without it the brand onboards looking complete and the agent still cannot work its tickets: the agent service treats these fields as optional and silently skips the write, so the gap only surfaces days later as "the agent isn't picking our tickets up". This page requires them for that reason.
The account must already be able to run neo list for this brand — onboarding stores the login, it does not create or test it.
Encrypted at rest by the agent service and never read back by this page.
Pick a cluster URL in step 1.
Derived from the cluster URL, not typed — apac.api is cluster in and only apac2.api is asia. Getting that pair the wrong way round mints the token for one cluster and calls another, and every request 401s.

Onboard

Fill Org ID, Brand and Cluster.
Validate first — a clean dry run unlocks this.

Already onboarded

Loading…
Secrets are masked at the source and re-masked by this server — the key tail is shown only so two keys can be told apart.