Set up a sign-in code
Find the authenticator-app option at the service you use. Check whether the service lets your account add a time-based code and whether an administrator needs to enable it.
Choose a setup guide
- Set up two-factor sign-in codes with KeySignerAdd a time-based code for a test GitHub, GitLab, Cloudflare or Bitwarden account. Verify the code at setup and again when you sign in.
- Two-factor codes for PyPI, RubyGems and Docker HubAdd a two-factor code to a test package registry account and check the next browser sign-in.
- Two-factor codes for DigitalOcean, Akamai and ScalewayAdd a time-based code for a test cloud dashboard user and keep a separate way to recover access.
- AWS IAM authenticator setupPair KeySigner with a sandbox AWS IAM user, enter two consecutive codes at enrollment, and check a fresh console sign-in.
- Set up Keycloak one-time codesAdd a Keycloak test account to KeySigner and check that Keycloak accepts a one-time code during setup and at a fresh sign-in.
- Set up sign-in codes for Gitea, Forgejo and CodebergAdd a time-based code for a test account, save its recovery key, and confirm the next browser sign-in before changing an account you rely on.
- Two-factor codes for Vultr, OVHcloud, Oracle Cloud and Proxmox VESet up a time-based sign-in code for a test hosting account. Follow the provider’s documented enrollment and recovery steps, then verify access with a fresh code.
- Sign-in codes for Salesforce, PingOne, JumpCloud and Auth0Add a time-based code for a test account in KeySigner, then test a fresh sign-in and check that you can still recover access independently.
- Sign-in codes for Google and Microsoft accountsTest a KeySigner authenticator code with Google Workspace, Google Cloud, Microsoft Entra ID or Azure. Use a test account whose policy allows codes, then check that the code works in the app you plan to use.
- Replace a Keycloak one-time codeReplace a test authenticator in Keycloak. Check which sessions remain after you remove it, then verify that Keycloak rejects the old code and accepts the replacement.
- Sign-in codes for Bitbucket Cloud, Buildkite, and SourceHutSet up a KeySigner code for a test account, save the provider’s recovery codes, and check that you can sign in again from a fresh browser.
- Sign-in codes for Okta, OneLogin, miniOrange, and Oracle FusionFind your test account’s authenticator setup, save it in KeySigner, and check that the provider accepts a new code from a fresh browser.
- Test a HashiCorp Vault sign-in code with KeySignerProtect a test user’s password sign-in with a code from KeySigner. Check that Vault requires the code, issues a token for the right user, and restores the prior sign-in when the pilot rule is removed.
- Test a Teleport authenticator code with KeySignerEnroll an authenticator for a local test user on a self-hosted Teleport cluster, then check that a fresh browser session opens with a code from KeySigner.
- Replace Gitea and Forgejo sign-in codesReplace the authenticator for a test account. Check whether an existing browser session stays open, then verify that the old code fails and a fresh replacement code works.
- Sign-in codes for LastPass, NetIQ, and PingFederateAdd a test account to KeySigner using your provider’s authenticator setup. Then check that the LastPass vault or the app you intend to use accepts a fresh code.
- Sign-in codes for BambooHR and CleverAdd an employee’s BambooHR 2-Step Login or a teacher or staff member’s Clever Classroom MFA to KeySigner. Use a test account and check that a fresh code opens the right BambooHR site or school portal.
- Test a Shibboleth sign-in code with KeySignerImport an operator-issued authenticator setup link into KeySigner. Check the code first, then verify that it opens the specific institutional app you intend to use.
- Replace a HashiCorp Vault sign-in codeReplace a test user’s Vault sign-in code with KeySigner. Check which code Vault accepts and whether the old token can still reach the same test record.
- Sign-in codes for CircleCI and SailPointSave a test account’s sign-in code in KeySigner, confirm it in CircleCI or SailPoint, and try the same account in a fresh browser.
- Verify OpenStack Keystone sign-in codesUse a test OpenStack project to check whether Keystone requires a password and a KeySigner code before issuing a project token.
- Test a Jenkins sign-in codeUse a disposable Jenkins user to check that the OpenMFA plugin accepts a code from KeySigner and preserves the user’s permissions.
- Sign-in codes for crates.io, NuGet.org, and GitLab CIAdd a maintainer’s sign-in code to KeySigner, then confirm the same account still reaches your package or pipeline in a fresh browser.
- Test an Azure DevOps sign-in codeUse a test Azure DevOps Services organization to confirm that KeySigner can provide a code for the account you use to open an Azure Repos project.
- Test a Gerrit sign-in codeCheck that a Keycloak-backed Gerrit test site accepts a code from KeySigner and opens the intended Gerrit reviewer account.
- Test an Ubuntu One sign-in codeUse a test Ubuntu One account to confirm that a KeySigner code opens the same Launchpad profile in a fresh browser.
- Test a Debian Salsa sign-in codeUse an activated local Salsa account to confirm that a KeySigner code opens the intended Debian project in a fresh browser.
- Test a Hetzner Console sign-in codeUse a test Hetzner account to check a KeySigner code and reopen the intended Cloud project.
- Test a Smallstep certificate requestUse a KeySigner code with Keycloak and check that a test Smallstep authority issues a short-lived certificate for the intended identity.
- Test Kubernetes access with a KeySigner codeUse a KeySigner code with Keycloak and check which resources the resulting account can read in a test Kubernetes cluster.
- Test a Breathe HR sign-in codeUse KeySigner to generate a code for a Breathe test employee. Check that the employee can open the right People Portal account in a fresh browser.
- Test a Fourth Engage sign-in codeUse KeySigner with the authenticator app method for a Fourth Engage test user. Check that a fresh code opens the intended location.
- Test ClassLink and Idira Identity sign-in codesUse KeySigner to generate a code for one test account in ClassLink LaunchPad or Idira Identity (formerly CyberArk Identity). Check that the code works in a fresh browser session.
- Test a Workday Central Login codeConnect KeySigner as the authenticator for one Workday Central Login test account, then verify a fresh sign-in and confirm how you would recover access.
- Test an Access PeopleHR sign-in codeUse KeySigner as the authenticator for one test user who opens PeopleHR through Access Identity. Check the web sign-in and keep a recovery method the test user can reach separately.
Check your result
Confirm enrollment and try a fresh sign-in. Check that the service accepts a new code and that your independent recovery method is still available.