Checking your session...
Checking your session...
Sign in with your Adtran OKTA account to onboard a customer onto the outage notification service.
Written automatically by step 1, when the gocare_base_credentials
secret exists in this account.
gocare_base_credentials secret, so step 1
cannot back the credential up. That is an account-level gap, not a missed
step for this tenant — the registry entry itself is still valid.
Reads both secrets back. Worth running even when a write reported success — this is the only check that catches a value that saved fine but that ONS will reject at delivery time, silently, with no metric and no DLQ.
gocare_secret is ONS's entire tenant registry — one flat JSON object of
<tenant>_url / <tenant>_auth pairs. A write here
takes effect on ONS's next invocation; no deploy is involved.
| Tenant | GoCare URL | Credential | State | Issues |
|---|
Each tenant needs one ads2s key with an m1api scope, which
is also the SHARED SECRET for the noc360.net webhook registration. Listing and
minting both require your own Okta token to carry AKS
super_user; this portal holds no key-minting credential of its own.
Editing and revoking live in the AKS admin portal, not here.
| Name | ID | Tenants | Created | Expires |
|---|
Every ONS error path increments WebhookFailure as well as its
own counter, so these four totals do not sum.
VisibilityTimeout is 0) but still increments its receive count.
| Queue | Available | In flight | Queue URL |
|---|