Access and credential onboarding¶
How engineers and partners request environments, keys, identifiers, test data, and support access.
Owner confirmation required
Several rows below depend on MasteryHive operations, security, or account owners. Where the repository does not define a ticket queue or SLA, the cell says Requires confirmation.
Who requests what¶
| You are | Typically request |
|---|---|
| Partner / client engineer | Non-production environment access, auth material, tenant/partner ids, sample payloads, support channel |
| MasteryHive engineer | Cloud project access, Secret Manager / key material, internal docs Access, infra identities (via owners) |
| Evaluator | Public docs + optional sandbox (if offered) |
Request checklist¶
| Item | Partner | MasteryHive engineer | Status in docs |
|---|---|---|---|
| Target environment (dev / staging / sandbox / prod) | Yes | Yes | Names in Environments; URLs Requires confirmation |
| Public keys for Fraud bidirectional JWT | Yes (exchange with MasteryHive) | Yes | Mechanism documented; issuance process Requires confirmation |
Tenant id / partner id / test userIds |
Yes | Yes | Field names documented; values Requires confirmation |
| Test data (customers, statements, documents) | Yes | Yes | Requires confirmation per programme |
| API base URLs | Yes | Yes | Requires confirmation per environment |
| Internal docs (Engineering / Troubleshoot / ADRs) | Rarely | Yes | Cloudflare Access — Requires confirmation |
| Support / on-call channel | Yes | Yes | Requires confirmation (account team) |
| Cloud console / logs / messaging | No (usually) | Yes | Infra owners — Requires confirmation |
Fraud key exchange (pattern)¶
- Agree environment and service audience (
iss/audas in Auth and tenancy). - Exchange public keys only through the channel MasteryHive security designates.
- Configure your backend to mint inbound tokens and verify outbound report tokens.
- Validate with a non-production scoring call before production.
Private keys must never appear in tickets, chat, or this documentation site.
KYC and Reconciliation¶
- KYC: confirm gateway or network requirements for the environment; do not assume anonymous internet access is approved.
- Reconciliation: obtain
partner_id/tenant_idscope values and confirm whether resolve is via messaging, HTTP, or both in that environment.
How to open a request¶
Until a public ticketing URL is published, contact your MasteryHive account owner or engineering manager and include: organisation, product(s), environment, named contacts, and whether you need public-docs-only or internal-docs access.
Requires confirmation: canonical request form, SLA, and security review checklist.