Keycloak + KeySigner

Protect administrators of a self-managed realm and keep application changes recoverable.

What to check first

Choose a test realm, confirm the account and verification settings, and check how another administrator can undo a lockout.

Choose a KeySigner setup

Setup guide What it does and what to keep available
Test a Keycloak one-time code →

Enroll KeySigner as an authenticator for a disposable Keycloak user and verify a fresh sign-in.

You need KeySigner on iPhone or Mac with Sign-in codes.

Keep available Keep a separate administrator who can manage the test user and its credentials.

Replace a Keycloak one-time code →

Replace an existing authenticator, end active sessions, and check which code Keycloak accepts.

You need KeySigner on iPhone or Mac with Sign-in codes.

Keep available Keep independent administrator access and the original KeySigner entry until you verify the replacement.

KeySigner setup requirements →

Provider availability

Time-based codes in a Keycloak realm. A realm administrator can require Configure OTP for one test user. Check provider requirements →

What it covers

Realm administrators and server operators have different ways to change access.

Make an offline recovery plan →

Troubleshooting

Did a change to the test realm have no effect on the app?

Compare the realm in the app's login URL with the realm you edited, then inspect the flow assigned to the client used in the test.

Ask your Keycloak operator to check the affected deployment, realm, and service logs for the failing request.

Find documentation and support →

Documentation and support

Keycloak documentation

Review realm and administrator settings
Set up or reset a one-time code

KeySigner setup help

Ask about this setup →