Trial Environment¶
All three tutorials run against a Cryptera trial environment. This page describes what it contains.
The trial is for evaluation only
Trials use the Keyserver's built-in Authserver so you can start without configuring an identity provider. Production deployments must authenticate through an external OAuth2/OIDC provider, such as Azure Entra ID or GitLab OIDC. See the Authentication Model.
Three services, three hostnames¶
A trial is one deployment exposed as three separate hostnames. <UNIQUE-ID> is your instance identifier. It appears in the getting-started email, and in the address bar once you log in.
| Service | URL | What it is |
|---|---|---|
| Admin UI | https://keyclient.<UNIQUE-ID>.cryptera-security.io | The browser interface: keys, roles, subjects, approvals, audit log |
| REST API | https://keyserver.<UNIQUE-ID>.cryptera-security.io | What pipelines and provisioning tools call |
| Authorization server | https://authserver.<UNIQUE-ID>.cryptera-security.io | Issues the tokens; the token endpoint is /oauth2/token |
The tutorials set the last two as shell variables:
export KEYSERVER="https://keyserver.<UNIQUE-ID>.cryptera-security.io"
export AUTHSERVER="https://authserver.<UNIQUE-ID>.cryptera-security.io/oauth2/token"
Seeded identities¶
Browser users log in interactively at the Admin UI. You never handle their tokens.
| User | Roles on a fresh trial | Purpose |
|---|---|---|
adminuser | Full administrator | Log in here to configure the system: keys, roles, subjects |
approver-fw | None pre-attached | The human approver. Attach an approver role scoped to your key, then approve as this user |
Client-credentials clients authenticate from the command line or a pipeline with a client ID and secret, and receive an access token.
| Client | Roles on a fresh trial | Purpose |
|---|---|---|
fw-client | QUICKSTART_FW | The CI/CD signing identity, already wired to fw-quickstart so it can sign immediately |
devicecert-client | None pre-attached | The provisioning identity. Attach a devcertsigner role for your CA key |
Trial credentials
Every identity uses the password password on standard trials. Check your getting-started email if your trial was configured differently.
Subjects are not accounts
The trial Authserver cannot register new identities, so the tutorials edit these seeded subjects. See Subjects are not accounts.
Seeded keys¶
| Key | Type | Algorithm | Approvers | Notes |
|---|---|---|---|---|
fw-quickstart-root | ROOT | EC secp256r1 / SHA256 | 0 | Trust anchor. fw-client can read its certificate to validate a full chain, but cannot sign with it |
fw-quickstart | FW | EC secp256r1 / SHA256 | 0 | The quick-start signing key. Zero approvers, so sign orders complete immediately |
Both are HSM-backed, so their private keys cannot be exported.
Switching identity in the browser¶
Once you sign in, the authorization server remembers you, and the login page offers to continue as that user instead of showing a blank form.
To act as a different person, for example to approve as approver-fw after configuring as adminuser, do one of:
- Open a private/incognito window, or
- Use a separate browser profile, or
- Sign out of the Keyserver UI first, and confirm you are prompted for a username
You need this in Sign Code Using the Trial Environment (Part 2), where you configure as an administrator and then approve as an approver.
What is shared, and what you change¶
A trial instance is shared state. Anything you create stays until you remove it, and anything you reconfigure stays reconfigured for whoever uses the instance next.
- Signing keys are never deleted, only revoked. A revoked key keeps its Key ID and its HSM Key ID, and neither can be reused. Pick a fresh Key ID and a fresh HSM Key ID each time.
- HSM Key IDs must be unique across all keys, revoked ones included. They are four hex digits in
0100–FFFE. The seeded keys use0200and0201. The tutorials reserve0100–0103:0100/0101in Admin Configuration (Part 1) and0102/0103in Issue a Device Certificate (Part 3). These do not exist on a fresh trial; you create them as you work through the tutorials. - Deleting a role, subject, or datastore entry cannot be undone. Re-using the name creates a fresh, empty record. See Manage Subjects in the Keyserver and Manage the Datastore.
- Part 2 temporarily changes a seeded key. Sign Code Using the Trial Environment (Part 2) raises
fw-quickstart's Required Approvers from 0 to 1. Step 16: Restore the Quick-Start Key sets it back to 0 and detaches the temporary approver role. If you stop partway, restore both by hand, or the zero-approval quick start stays off for the next user.
If an instance has drifted too far to be useful, ask Cryptera to reset it.
Where to start¶
Each tutorial runs on its own. Part 1 is recommended first, but not required.
| You are | Start with |
|---|---|
| An administrator setting the system up | Admin Configuration (Part 1) |
| A developer who wants a signature | Sign Code Using the Trial Environment (Part 2) |
| A provisioning engineer issuing device identities | Issue a Device Certificate Using the Trial Environment (Part 3) |