KeySigner setup requirements

Find the devices, builds and accounts you need for KeySigner setups and provider walkthroughs.

Prepare an account recovery worksheet →

Plan a pilot with the rollout checklist →

Which KeySigner plan fits your setup?

Personal
Free for your own keys and accounts. Use a personal signing rule to approve actions such as signing your own Git commits.
Teams
Quoted per seat for teams that protect shared accounts or assign YubiKeys by serial number.

Check the provider requirements below for any plan, account type or policy the app itself requires.

Check provider availability

Confirm which plans, account types and environments support the feature you want to use.

1Password

Unlock 1Password with Okta. Requires 1Password Business and 1Password 8.

Confirm that you can administer both accounts and that the pilot user has the same email address in both. Keep an owner available for recovery.

Cloudflare

Cloudflare dashboard access through Okta. Available on all Cloudflare plans.

Use a domain you control, a Cloudflare Zero Trust organization, and a super administrator who can use the Cloudflare API.

GitHub Actions

Required deployment reviewers. Available for public repositories on current plans. Private or internal repositories require GitHub Enterprise.

Check the visibility of the repository and open Settings → Environments. Confirm that the release environment lets you configure required reviewers.

npm

Trusted publishing from GitHub Actions. Requires a GitHub-hosted runner for this workflow.

Look at the runner recorded for the publishing job. For automatic provenance, also check the visibility of the repository and the package.

Bitbucket

Blocking merges when checks fail. Requires Bitbucket Cloud Premium.

Under Branch restrictions, confirm that the destination branch has Prevent a merge with unresolved merge checks enabled.

GitLab

Required deployment approvals. Requires GitLab Premium or Ultimate for a protected environment.

Open Settings → CI/CD → Protected environments. Check approval rules for the environment the publishing job uses. This applies if you add a deployment approval to the rehearsal.

PyPI

Trusted publishing from GitLab. Requires a project hosted on GitLab.com.

In the TestPyPI project’s publishing settings, match the GitLab project path and the top-level pipeline file.

Breathe HR

Authenticator app setup for a test employee. The prompt depends on the account role and Breathe settings. Paid subscriptions automatically enable two-factor authentication for Admin and HR roles.

For a regular employee, check whether a prompt is required or whether Enable 2FA is available in User preferences.

Fourth

Authenticator app codes for Fourth Engage. The test user needs the authenticator app setting in Fourth360.

An individual setting can override the organization setting. Check the effective method and use the current Engage login.

Duo

Passkey for the second verification step. Depends on the effective Duo policy and the type of authenticator the browser or device offers.

Check app and group policy for Platform authenticators or Roaming authenticators before enrolling.

Okta

Authenticator app codes in Okta Identity Engine. The enrollment policy for the test user must allow the Google Authenticator method.

In Security → Authenticators, check that the method is listed under Setup and available to the user under Enrollment. Check that the target app’s authentication policy accepts it.

Microsoft Entra ID

Codes from a third-party authenticator app. The Authentication methods policy must allow Third-party software OATH tokens for the test user.

Ask an Authentication Policy Administrator to check the user’s policy and the target app’s requirements. The built-in Phishing-resistant MFA strength excludes software OATH codes.

Google Workspace

Authenticator app codes for 2-Step Verification. The Only security key setting accepts security keys and passkeys and excludes authenticator app codes.

In the Google Admin console, check the 2-Step Verification Methods setting that applies to the test user’s group or organizational unit.

JumpCloud

Time-based codes for the JumpCloud User Portal. The organization must enable time-based codes for the User Portal.

Check the test user’s MFA settings and enrollment deadline in the Admin Portal. If required enrollment expires, the user loses User Portal access until an administrator restores it.

Keycloak

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

Check that the realm uses time-based codes and that the browser authentication flow prompts for a code after enrollment.

Check versions before setup

Google Chrome

Chrome 111 or later for the development extension.

Open Help, then About Google Chrome, to see the installed browser version. After loading the unpacked extension, check that it is enabled in the profile you use for the test.

Find your Chrome version · Open the setup guide

Firefox

Firefox 128 or later for the temporary development add-on.

Open about:support and look under Application Basics for Version and Update Channel. After restarting Firefox, load the temporary add-on again in the profile you use for the test.

Find your Firefox version · Open the setup guide

YubiKey

Firmware 5.3.0 or later to add a new KeySigner unlock key. Your configured minimum can be higher.

Connect the key and open Home in Yubico Authenticator on desktop or Android. Read the firmware version for the connected key before enrolling it.

Find your YubiKey firmware · Open the setup guide

KeePassXC

KeePassXC 2.8.0 was used for the local key-file recovery test.

Check the app version with keepassxc --version where the app command is available. If your version differs, verify that you can open a disposable database with the restored key file before trying it with a database you rely on.

KeePassXC version command · Open the setup guide

Safe

Safe contract versions 1.3.0, 1.4.1 and 1.5.0 are recognized by KeySigner’s Safe connection. The owner approval rehearsal uses 1.4.1.

Open the test Safe on the intended network, then go to Settings and Contract version. Use an existing test Safe that matches the rehearsal before changing any contract settings.

Safe contract version in Settings · Open the setup guide

Azure DevOps

Azure DevOps Services.

Open the test organization at dev.azure.com and check which Microsoft or GitHub account the organization uses. This guide covers the hosted service.

Compare Azure DevOps Services and Azure DevOps Server · Open the setup guide

Gerrit

Tested on Gerrit 3.13.11 with the OAuth provider plugin at 5c230cddba and Keycloak 26.8.2.

Check the Gerrit version and installed OAuth plugin in your test instance. In the Keycloak Admin Console, confirm the version, realm and client used by Gerrit.

Gerrit 3.13 releases · Open the setup guide

KeySigner setups

Tool Setup and requirements

Compare GitHub setups →

Approve a Git commit on your phone

Computer tools and KeySigner on iPhone

Pair the KeySigner computer tools with the phone and add the public key to GitHub as a signing key. Use a test repository to check the signature in Git and on GitHub.

Verify a signed change on GitHub →
Test a time-based sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a disposable GitHub.com personal account. In Settings → Password and authentication, enable two-factor authentication and open the setup QR code. Save the recovery codes before finishing.

Set up two-factor sign-in codes with KeySigner →
Require a YubiKey to unlock a signing key

KeySigner on iPhone and a YubiKey

New unlock-key enrollment needs readable firmware version 5.3.0 or later and a key that meets your configured minimum and enrollment settings. Keep a separate recovery method available.

Test a KeySigner approval that requires a YubiKey →

Compare Safe setups →

Propose or confirm a Safe transaction

KeySigner on iPhone and a WalletConnect-enabled app

Use Safe 1.3.0, 1.4.1 or 1.5.0. Check the network and that your KeySigner key is a current owner. Execution requires the Safe's configured number of owner confirmations.

Propose a Safe transaction from a WalletConnect app →
Rehearse a proposal and execution with Safe owners

Computer tools, KeySigner on iPhone and a local test network

Use a disposable Safe 1.4.1 with a threshold of two, an independent co-owner, paired KeySigner computer tools, a transaction service for the test network, and test gas for the executor.

Rehearse a two-owner approval in Safe →
Receive a wallet request on your phone

KeySigner on iPhone and a WalletConnect-enabled app

Keep KeySigner open on your phone to receive plain-message, typed-data or transaction requests. The app must offer WalletConnect on Ethereum, Base, Arbitrum One, OP Mainnet, Polygon, Sepolia or Base Sepolia.

Propose a Safe transaction from a WalletConnect app →

Compare Google Chrome setups →

Connect a test app and approve a wallet request

Desktop Chrome, the development extension and KeySigner on iPhone

Load the development extension folder in Chrome. The extension requires Chrome 111 or later. Pair the computer tools with the phone and use an Ethereum test key and a trusted test app that recognizes browser wallets.

Approve an Ethereum request from Google Chrome →
Add and switch a local Ethereum network

KeySigner computer tools, Anvil and Python 3

Use Chrome 111 or later and load the unpacked development extension in a separate browser profile.

Test an Ethereum network in your browser →
Retest an existing test site connection

Desktop Chrome, the development extension and KeySigner on iPhone

Use Chrome 111 or later, pair the computer tools with the phone, and use a disposable Ethereum account and trusted test site.

Retest an Ethereum site connection in Chrome or Firefox →
Build and test a browser wallet connection in Chrome

Desktop Chrome 111 or later and the KeySigner development extension

Use the development extension in a separate Chrome profile. Open the example at the local address in the guide.

Build a KeySigner browser wallet integration →

Compare Ethereum setups →

Approve an Ethereum test message

KeySigner on iPhone and a WalletConnect-enabled test app

Use an Ethereum key in KeySigner and a test app that offers WalletConnect on a network KeySigner can use. The test app needs a way to verify the signature against the account you select.

Approve an Ethereum test message with WalletConnect →
Send a test ERC-20 token

Computer tools, KeySigner on iPhone and an Ethereum test network

Use a known ERC-20 test contract, a test recipient and a test account with both the token and test ETH for fees. Check the contract address on the selected network.

Send an Ethereum test token with KeySigner →
Review a .eth recipient address

KeySigner computer tools, KeySigner on iPhone and a local Ethereum test network

Pair the computer tools with the phone. Fund a test account and set up a plain-ASCII .eth name on a local chain with an ENSv1 registry and a direct Ethereum address record.

Check an ENS recipient before sending Ethereum →
Build and test a browser wallet connection

KeySigner on iPhone with a test Ethereum account

Pair the KeySigner computer tools with the phone and use a disposable Ethereum account with no funds. Install Python 3 to serve the local file and Foundry to verify the signature with cast.

Build a KeySigner browser wallet integration →

Compare Firefox setups →

Approve a request in Firefox

Desktop Firefox, the temporary development add-on and KeySigner on iPhone

The development add-on requires Firefox 128 or later. Pair the computer tools and reload the add-on each time Firefox restarts. Use a test Ethereum key and a trusted test app that recognizes browser wallets.

Approve an Ethereum request from Firefox →
Add and switch a local Ethereum network

KeySigner computer tools, Anvil and Python 3

Use Firefox 128 or later and load the temporary development add-on in a separate browser profile.

Test an Ethereum network in your browser →
Retest an existing test site connection

Desktop Firefox, the temporary development add-on and KeySigner on iPhone

Use Firefox 128 or later. Pair the computer tools with the phone, reload the temporary add-on after restarting Firefox, and use a disposable Ethereum account and trusted test site.

Retest an Ethereum site connection in Chrome or Firefox →
Build and test a browser wallet connection in Firefox

Desktop Firefox 128 or later and the KeySigner development extension

Load the temporary development add-on in a separate Firefox profile. Open the example at the local address in the guide.

Build a KeySigner browser wallet integration →

Compare Bitcoin setups →

Sign a test payment with one key

Computer tools, KeySigner on iPhone and Bitcoin Core regtest

Pair the computer tools with KeySigner. Use a funded single-key native SegWit address and a transaction file that includes the amounts of the coins it spends. Rehearse on Bitcoin Core regtest.

Sign a Bitcoin test payment with one key →
Require multiple keys for a shared payment

Computer tools, KeySigner on iPhone and Bitcoin Core regtest

Use a shared Bitcoin wallet with an explicit threshold and its matching wallet descriptor. Each input needs signatures from the required number of members. Use a new regtest wallet and test coins.

Test a shared Bitcoin payment that needs two keys →
Test copying a time-based code from 1Password

KeySigner macOS build with password-manager import enabled

Use a local 1Password 8 1PUX export no larger than 16 MiB from a test vault.

Test importing codes from a password manager →
Test copying a time-based code from KeePass

KeySigner macOS build with password-manager import enabled

Use a local KeePass 2 XML export no larger than 16 MiB from a test database.

Test importing codes from a password manager →

Compare KeePassXC setups →

Test copying a time-based code from KeePassXC

KeySigner macOS build with password-manager import enabled

Use a local KeePassXC 2.8.0 command-line XML export no larger than 16 MiB and choose KeePass XML in KeySigner.

Test importing codes from a password manager →
Create and recover a test database key file

KeySigner macOS test build with local key file commands and KeePassXC 2.8.0

Use a disposable KeePassXC database with a password, an empty KeySigner key file store in a separate test setup, and private local folders for the XML key file and encrypted backup.

Recover a KeePassXC key file →
Copy time-based sign-in codes

KeySigner for iPhone or Mac with Google Authenticator import

Unlock Sign-in codes and use a disposable account with its own recovery option. Have a second screen for the export QR code or a private local QR image. Have the signers you need to approve a code.

Import time-based codes from Google Authenticator →
Test a time-based sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a disposable GitLab account with a verified email. Open Edit profile → Access → Password and authentication, then register a one-time password authenticator. Save the recovery codes GitLab gives you.

Set up two-factor sign-in codes with KeySigner →
Test a time-based sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a disposable Cloudflare dashboard profile. In Profile → Authentication, open Two-Factor Authentication, then add Mobile App Authentication. Have your Cloudflare password available and save the backup codes.

Set up two-factor sign-in codes with KeySigner →
Test a time-based sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a disposable Bitwarden web vault. In Settings → Security → Two-step login, open Authenticator App settings. Have your master password available and save the recovery code outside this vault.

Set up two-factor sign-in codes with KeySigner →
Test a PyPI authenticator code

KeySigner on iPhone or Mac with Sign-in codes

Use a test PyPI account. In account settings, generate recovery codes and verify one before choosing Add 2FA with authentication application. PyPI allows one authenticator app per account and recommends a security device where possible.

Two-factor codes for PyPI, RubyGems and Docker Hub →
Test a RubyGems sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test RubyGems.org account with no gems. Open edit settings, then Multi-factor Authentication and Authentication App. Register a device and have secure storage ready for the recovery codes shown after setup.

Two-factor codes for PyPI, RubyGems and Docker Hub →

Compare Docker Hub setups →

Test a Docker Hub browser sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use an individual Docker account with a verified email and have your password available. Docker documents this for Personal and Pro. Go to Account settings → 2FA and save the single recovery code before scanning the QR code.

Two-factor codes for PyPI, RubyGems and Docker Hub →
Check an approved multi-platform image

Docker Buildx, jq, a SHA-256 tool and a KeySigner test release workflow

Register the package under docker.io with its namespace/repository name. Configure both test release owners and keep access to the exact approved digest. The public rehearsal works without a Docker Hub account.

Check an approved Docker Hub image digest →
Test a DigitalOcean dashboard sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test user who signs in with a DigitalOcean username and password. In My Account → Two-factor authentication, choose Set Up 2FA and the authentication app option. Select backup codes when asked for a backup method.

Two-factor codes for DigitalOcean, Akamai and Scaleway →
Test an Akamai Cloud Manager sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test user whose login method is Cloud Manager. Go to Login & Authentication, check that all three security questions are configured, then enable Two-Factor Authentication. Save the scratch code when setup completes.

Two-factor codes for DigitalOcean, Akamai and Scaleway →
Test a Scaleway console sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test Owner or IAM Member with the required permissions. From your profile menu, open Settings. Under Account security, choose One-time password, then Set up TOTP. Save the backup codes after setup.

Two-factor codes for DigitalOcean, Akamai and Scaleway →
Test two consecutive AWS enrollment codes

KeySigner on iPhone or Mac with Sign-in codes

Use an IAM test user with MFA enrollment permission in a sandbox account. Keep an independent MFA device or an administrator available. AWS recommends a passkey or security key where possible.

AWS IAM authenticator setup →

Compare Keycloak setups →

Test a Keycloak one-time code

KeySigner on iPhone or Mac with Sign-in codes

Use a non-admin user in a disposable Keycloak realm with the default time-based OTP policy. Have a separate realm administrator who can reset the test credential, plus the signers your KeySigner rule requires.

Set up Keycloak one-time codes →
Replace a Keycloak one-time code

KeySigner on iPhone or Mac with Sign-in codes

Use a disposable realm, one non-admin test user with a working code and a separate administrator with credentials and session permissions. Keep the original KeySigner entry until you check the replacement.

Replace a Keycloak one-time code →

Compare Gitea setups →

Test a Gitea browser sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a non-admin test user on a test instance. In Settings → Security, choose Enroll in Two-Factor Authentication. Save the single-use recovery key and have the signers your rule requires available.

Set up sign-in codes for Gitea, Forgejo and Codeberg →
Replace a Gitea browser sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use an enrolled non-admin test account on a local instance. Keep a signed-in Security tab, the old KeySigner entry and an independent recovery route until the replacement works in a fresh session.

Replace Gitea and Forgejo sign-in codes →

Compare Forgejo setups →

Test a Forgejo browser sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a non-admin test user on a test instance. In Settings → Security, choose Enroll into two-factor authentication. Save the single-use recovery key and have the required signers available.

Set up sign-in codes for Gitea, Forgejo and Codeberg →
Replace a Forgejo browser sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use an enrolled non-admin test account on a local instance. Keep a signed-in Security tab, the old KeySigner entry and an independent recovery route until the replacement works in a fresh session.

Replace Gitea and Forgejo sign-in codes →
Set up a Codeberg browser sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test account you control. Codeberg documents a six-digit time-based code in Settings → Security. Save the scratch token separately before checking a fresh sign-in.

Set up sign-in codes for Gitea, Forgejo and Codeberg →
Test a Vultr console sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test account that signs in with its Vultr password. Have a secure place for the separate emergency backup codes.

Two-factor codes for Vultr, OVHcloud, Oracle Cloud and Proxmox VE →
Test an OVHcloud Control Panel sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test profile with access to account security. Have secure storage ready for the first set of backup codes or confirm you still have an unused code from an earlier setup.

Two-factor codes for Vultr, OVHcloud, Oracle Cloud and Proxmox VE →
Test an Oracle Cloud identity domain sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test user in an IAM identity domain that allows Mobile App Passcode. Have a bypass code or a separate domain administrator available for recovery.

Two-factor codes for Vultr, OVHcloud, Oracle Cloud and Proxmox VE →
Test a Proxmox VE web sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a non-admin test user on a test instance in a realm that allows user-configured TOTP. Keep a separate administrator available and use the same realm for enrollment and sign-in.

Two-factor codes for Vultr, OVHcloud, Oracle Cloud and Proxmox VE →
Test a Salesforce sandbox sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a non-privileged sandbox user whose rules allow authenticator app codes. Keep a second registered verification method and confirm who can issue an MFA temporary verification code.

Sign-in codes for Salesforce, PingOne, JumpCloud and Auth0 →
Test a PingOne end-user sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test end-user account in an environment that offers Authenticator app in My Profile. Keep an independent method accepted by that same application.

Sign-in codes for Salesforce, PingOne, JumpCloud and Auth0 →
Test a JumpCloud User Portal sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test User Portal account with TOTP enrollment enabled. Keep a separate JumpCloud administrator available to reset the user’s enrollment if necessary.

Sign-in codes for Salesforce, PingOne, JumpCloud and Auth0 →
Test a code in an Auth0 application

KeySigner on iPhone or Mac with Sign-in codes

Use a test application in a separate Auth0 tenant. Configure Universal Login to require MFA with One-time Password and Recovery Code available. Save the recovery code securely outside the account in the test.

Sign-in codes for Salesforce, PingOne, JumpCloud and Auth0 →
Test a Google Workspace authenticator code

KeySigner on iPhone or Mac with Sign-in codes

Use a test Workspace user whose organizational unit or group allows authenticator codes. Check that an independent verification or recovery method is available.

Sign-in codes for Google and Microsoft accounts →
Test an authenticator code at the Google Cloud console

KeySigner on iPhone or Mac with Sign-in codes

Use a non-admin account that signs in directly with Google and can view a sandbox project. Keep the existing verification method available.

Sign-in codes for Google and Microsoft accounts →
Test an Entra ID authenticator code

KeySigner on iPhone or Mac with Sign-in codes

Use a tenant test user included in Third-party software OATH tokens. Check the authentication strength for the intended app and keep an independent method available.

Sign-in codes for Google and Microsoft accounts →
Test an authenticator code at the Azure portal

KeySigner on iPhone or Mac with Sign-in codes

Use a tenant test user with read access to a sandbox resource and a policy that permits software OATH codes for the portal. Keep independent recovery available.

Sign-in codes for Google and Microsoft accounts →
Troubleshoot an approval before publishing

KeySigner console and enrolled owner approval tools

Use a disposable package and a GitHub Actions workflow already configured to wait for KeySigner. Have a separate requester, enough eligible owners and access to the workflow logs.

Troubleshoot a package release approval →
Compare approved and published package bytes

KeySigner console and access to the npm test package

Register the disposable package and its owner rule in KeySigner. Use the registry’s own publishing configuration and keep the approved digest and workflow run available for comparison.

Troubleshoot a package release approval →
Test a Bitbucket Cloud browser sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test account with a confirmed email and working Git access. Keep the original browser session open and save Bitbucket’s recovery codes separately.

Sign-in codes for Bitbucket Cloud, Buildkite, and SourceHut →
Test a Buildkite browser sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test account that signs in directly to Buildkite. Save the recovery codes before proceeding to the setup QR code.

Sign-in codes for Bitbucket Cloud, Buildkite, and SourceHut →
Test a SourceHut browser sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test account and keep the original browser session open. Save the recovery codes when SourceHut activates the method.

Sign-in codes for Bitbucket Cloud, Buildkite, and SourceHut →
Test an Okta Identity Engine authenticator code

KeySigner on iPhone or Mac with Sign-in codes

Use an Identity Engine test user whose enrollment and app policies allow Google Authenticator. Keep a second method or an administrator who can reset enrollment available.

Sign-in codes for Okta, OneLogin, miniOrange, and Oracle Fusion →
Test a OneLogin Authenticator code

KeySigner on iPhone or Mac with Sign-in codes

Use a test user whose OneLogin policy includes Authenticator. Verify from a fresh browser and keep a separate enrolled method or admin reset available.

Sign-in codes for Okta, OneLogin, miniOrange, and Oracle Fusion →
Test a miniOrange IAM authenticator code

KeySigner on iPhone or Mac with Sign-in codes

Use a miniOrange IAM test user whose profile offers Google Authenticator. Confirm an administrator can restore the prior method or reset enrollment before making a change.

Sign-in codes for Okta, OneLogin, miniOrange, and Oracle Fusion →
Test an authenticator code for an Oracle Fusion app

KeySigner on iPhone or Mac with Sign-in codes

Use a Fusion test account backed by an Oracle Cloud IAM identity domain that offers third-party authenticator enrollment. Keep a bypass code or independent recovery method available.

Sign-in codes for Okta, OneLogin, miniOrange, and Oracle Fusion →

Compare HashiCorp Vault setups →

Test a HashiCorp Vault sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a disposable Vault instance with a username and password test user, a separate recovery administrator, and access to run Vault API calls.

Test a HashiCorp Vault sign-in code with KeySigner →
Replace a Vault code and verify token revocation

KeySigner on iPhone or Mac with Sign-in codes and a Vault API client

Use a disposable Vault instance, one test user with working Login MFA, an independent administrator, and a test record. Keep the original authenticator entry and token in separate test clients until you verify the result.

Replace a HashiCorp Vault sign-in code →
Test a Teleport authenticator code

KeySigner on iPhone or Mac with Sign-in codes

Use a self-hosted test cluster that allows the Authenticator App method for a local test user. Keep an independent cluster administrator available.

Test a Teleport authenticator code with KeySigner →
Test a code for a LastPass vault

KeySigner on iPhone or Mac with Sign-in codes

Use a LastPass test vault that offers Google Authenticator in Multifactor Options. Confirm an independent recovery option before enrollment.

Sign-in codes for LastPass, NetIQ, and PingFederate →
Test an Advanced Authentication sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a NetIQ Advanced Authentication 6.4 test account with TOTP enabled and the third-party QR format. Have an administrator confirm the method is allowed for the target app.

Sign-in codes for LastPass, NetIQ, and PingFederate →
Test a code for a PingFederate app using PingID

KeySigner on iPhone or Mac with Sign-in codes

Use a test app whose PingFederate policy uses PingID with Authenticator App enabled. Keep an independent method available or arrange a reset with the help desk.

Sign-in codes for LastPass, NetIQ, and PingFederate →
Add a code for a BambooHR test employee

KeySigner and a browser

The test account needs BambooHR 2-Step Login with an authenticator app. Use the QR code that pairs the app and keep an available recovery method. If the site redirects authentication elsewhere, check the methods there.

Sign-in codes for BambooHR and Clever →
Add a code for a Clever teacher or staff account

KeySigner and a browser

The school must enable Classroom MFA and allow the App method for this test account. Confirm the school portal and keep a second method or a way to reach the administrator for a reset.

Sign-in codes for BambooHR and Clever →
Test an institution-issued sign-in code

KeySigner, a browser, and a Shibboleth operator

The operator needs a test account with an issued TOTP setup link and a test app whose flow uses the plugin. Confirm access recovery independently and test the app in a fresh browser.

Test a Shibboleth sign-in code with KeySigner →
Test a CircleCI sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a direct CircleCI email and password test account. Save CircleCI’s one-time recovery code separately.

Sign-in codes for CircleCI and SailPoint →
Test a SailPoint sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a test account on a SailPoint tenant configured for authenticator codes. Confirm how you can recover access before enrolling.

Sign-in codes for CircleCI and SailPoint →
Check a Keystone project token with a sign-in code

KeySigner on iPhone or Mac with Sign-in codes

Use a Keystone test environment, a disposable user with project read access, and a separate administrator account.

Verify OpenStack Keystone sign-in codes →
Test a Jenkins sign-in code

KeySigner on iPhone or Mac and a browser

Use an isolated Jenkins instance, a compatible OpenMFA release, a read-only local user and independent administrator access.

Test a Jenkins sign-in code →
Test a crates.io maintainer sign-in code

KeySigner on iPhone or Mac and a browser

Use the GitHub account linked to the crates.io test profile. Save GitHub recovery codes separately.

Sign-in codes for crates.io, NuGet.org, and GitLab CI →
Test a NuGet.org maintainer sign-in code

KeySigner on iPhone or Mac and a browser

Use the Microsoft account linked to the NuGet.org test profile. Confirm recovery access and whether your work or school account allows third-party authenticator codes.

Sign-in codes for crates.io, NuGet.org, and GitLab CI →
Test a GitLab CI maintainer sign-in code

KeySigner on iPhone or Mac and a browser

Use a GitLab test account with confirmed email and access to a test project. Save GitLab recovery codes separately.

Sign-in codes for crates.io, NuGet.org, and GitLab CI →
Test an Azure DevOps sign-in code

KeySigner on iPhone or Mac and a browser

Use an Azure DevOps Services test organization and the linked Microsoft or GitHub identity. The account needs read access to a test repository, an allowed authenticator code method, and an independent recovery option.

Test an Azure DevOps sign-in code →
Test a Gerrit sign-in code

KeySigner on iPhone or Mac and a browser

Use a Gerrit test site with its OAuth provider configured for Keycloak, a reviewer with test repository access, and a separately available administrator.

Test a Gerrit sign-in code →
Test an Ubuntu One sign-in code

KeySigner on iPhone or Mac and a browser

Use a test Ubuntu One account with a linked Launchpad profile, a time-based authentication device option, and a separate recovery method.

Test an Ubuntu One sign-in code →
Test a Debian Salsa sign-in code

KeySigner on iPhone or Mac and a browser

Use an activated, email-verified local Salsa account and a non-production project the account can read. Save the recovery codes that Salsa provides after enrollment.

Test a Debian Salsa sign-in code →
Test a Hetzner Console sign-in code

KeySigner on iPhone or Mac and a browser

Use a test Hetzner account with an existing Cloud test project and the mobile device authenticator option. Keep the recovery key or a separate working method.

Test a Hetzner Console sign-in code →
Test a Smallstep certificate request

KeySigner on iPhone or Mac, a browser and a certificate client

Use a test step-ca authority with a Keycloak-backed OpenID Connect provisioner, a non-admin operator who can request certificates, the CA root certificate, and separate administrator access to both systems. Confirm the provisioner and expected lifetime before testing.

Test a Smallstep certificate request →
Test Kubernetes access with a KeySigner code

KeySigner on iPhone or Mac, a browser and kubectl

Use a test cluster that trusts a Keycloak realm through OpenID Connect, a configured client, two test namespaces and an independent administrator. Give the test account permission to list pods in one namespace.

Test Kubernetes access with a KeySigner code →
Verify a signed npm archive and its KeySigner approval

KeySigner release history and Cosign

Have the test npm archive, its Sigstore bundle and the approved SHA-256 from the KeySigner request.

Check an approved package with Cosign →
Verify the publisher before checking approval

KeySigner release history and Cosign

Get the expected signing identity and OIDC issuer from your release policy.

Check an approved package with Cosign →
Test a Breathe HR sign-in code

KeySigner on iPhone or Mac and a browser

Use an authorized Breathe test employee with two-factor authentication available. Confirm that HR or an administrator can reset the employee’s method.

Test a Breathe HR sign-in code →
Test a Fourth Engage sign-in code

KeySigner on iPhone or Mac and the current Fourth Engage web login

Use an authorized test user with the authenticator app method, one test location, and a Fourth360 administrator who can reset access.

Test a Fourth Engage sign-in code →
Check and disconnect a read-only Aave wallet connection

Desktop Chrome 111 or later, the KeySigner development extension and a paired iPhone

Load the development extension in a separate browser profile. Use an unfunded Ethereum test account and leave other wallet extensions disabled in that profile.

Test a KeySigner wallet connection in Aave →
Check and disconnect a read-only Curve wallet connection

Desktop Chrome 111 or later, the KeySigner development extension and a paired iPhone

Use a separate browser profile and an unfunded Ethereum test address. Select Ethereum before opening the wallet picker.

Test a KeySigner wallet connection in Curve →
Check and disconnect a read-only Balancer wallet connection

Desktop Chrome 111 or later, the KeySigner development extension and a paired iPhone

Use a separate browser profile and an unfunded Ethereum test address. Stop at the account and policies check.

Check a KeySigner wallet connection in Balancer →
Verify a signed image and its KeySigner release approval

Notation, ORAS and KeySigner release history

Use a disposable image repository, a configured KeySigner test release workflow, the full approved OCI digest and the trusted publisher certificate.

Check an approved container image with Notation →
Check whether Uniswap detects KeySigner

Desktop Chrome 111 or later and the KeySigner development extension

Use a separate Chrome profile with other wallet extensions disabled. The check stops before sharing an address, granting token permissions or swapping.

Check if Uniswap detects KeySigner →
Check whether OpenSea detects KeySigner

Desktop Chrome 111 or later and the KeySigner development extension

Use a separate Chrome profile with other wallet extensions disabled. OpenSea excludes wallets that require multiple private keys to sign and send a transaction.

Check if OpenSea detects KeySigner →
Verify an RSA signature and compare the archive with the release approval

KeySigner release history and OpenSSL

Use a test npm archive, its detached RSA signature with SHA-256, the publisher’s trusted PEM key and the approved digest from KeySigner.

Check an approved npm archive with OpenSSL or GnuPG →
Verify the OpenPGP signer and compare the archive with the release approval

KeySigner release history and GnuPG with --assert-signer

Use a test npm archive, its detached OpenPGP signature, the independently verified publisher fingerprint and the approved digest from KeySigner.

Check an approved npm archive with OpenSSL or GnuPG →
Add Polygon Amoy and read the latest testnet block

KeySigner computer tools, desktop Chrome and Python 3

Use Chrome 111 or later, load the development extension in a fresh test profile, and connect to the internet to reach the public RPC.

Test Polygon Amoy with Tenderly and KeySigner →
Check a Solana test transfer

KeySigner source checkout and Rust 1.98 or later

Use disposable software keys for this offline exercise. It checks one legacy System Program transfer with one signer and uses no funded account.

Verify a Solana transfer with KeySigner →
Verify a workload token and test refusal

KeySigner source checkout, Node.js 26.6.0, Python 3, Rust 1.98.1 and wasm-pack 0.13.1

The example supplies a local test key service and two disposable keys. For live AWS permissions and key policies, use the separate AWS key access guide.

Rehearse an AWS KMS workload token →
Read a World Chain Sepolia block

Desktop Chrome, the KeySigner development extension and computer tools

Use a fresh browser profile, Python 3 for the local test page, and a connection to Alchemy’s public World Chain Sepolia endpoint. No Alchemy API key, wallet account or test ETH is required.

Connect KeySigner to an Alchemy test network →
Verify the publisher and exact RPM approved by the release owners

KeySigner release approvals, rpmkeys and GnuPG

Use two enrolled owners, a disposable signed RPM outside production repositories, and the publisher certificate with an independently verified fingerprint. Use an RPM build that supports the _pkgverify_level verification policy.

Verify a signed RPM against a KeySigner approval →
Test an Idira Identity authenticator code

KeySigner on iPhone or Mac and a browser

For Idira Identity, use an authorized test tenant and a user whose policy offers OATH OTP Client. Keep a separate method or an administrator who can reset the test credential.

Test ClassLink and Idira Identity sign-in codes →
Test a Workday Central Login authenticator code

KeySigner on iPhone or Mac and a browser

Use an approved Workday Central Login test account that can enroll an authenticator app. Keep access to the account’s verified recovery email.

Test a Workday Central Login code →
Test a PeopleHR authenticator code

KeySigner on iPhone or Mac and a browser

Use one Access Identity test user authorized to open PeopleHR. Confirm that its policy offers an authenticator app and that you have an independent place for the backup codes.

Test an Access PeopleHR sign-in code →

Provider walkthroughs

Check the provider plans, permissions and test accounts needed for these rehearsals.

Check another setup

Open the app page for provider requirements or check an unlisted app.

KeySigner for Mac and iPhone is in early access. Ask which build is available for the setup you want to try.

Explore all integrations →

Ask about a setup →