Integration setup guides
Choose a task to see what to prepare, what to test and how to check the result.
Browse by task
- Build a KeySigner browser wallet integrationRun a local website that discovers KeySigner, asks permission to see one Ethereum test account and requests a plain-text signature.
- Rehearse recovery for a 1Password accountFind out whether someone who loses a device can regain access to a 1Password account and open the vault they need.
- Pilot an Okta access policy without locking out adminsRun the same test with a pilot user and a backup administrator so you know what your policy covers and how you can roll it back.
- Verify a signed change on GitHubApprove a test commit on your phone, then check that GitHub marks the same commit as verified.
- Review the path from GitHub Actions to npmSeparate the person who approves a release from the workflow that publishes it. Rehearse the handoff before changing a real package.
- Review a Safe transaction with Tenderly simulationPreview a proposed transaction and compare the result with what your Safe owners plan to authorize.
- Test a KeySigner approval that requires a YubiKeyOn a supported KeySigner device, use a spare key and an expendable operation to confirm that a physical key is required to approve.
- Rehearse account recovery with 1Password and OktaCheck that your team can regain 1Password vault access when someone loses a device or access to Okta is interrupted.
- Rehearse Bitwarden recovery after losing a YubiKeyRegister a spare YubiKey for Bitwarden two-step login and make sure you can reach recovery information with the vault locked.
- Test Cloudflare dashboard access with OktaCheck the complete access and rollback path on a dedicated test domain before requiring Okta for Cloudflare dashboard access.
- Rehearse publishing to PyPI from GitLabRehearse a test release from a GitLab.com project and verify that TestPyPI trusts the intended pipeline.
- Rehearse an AWS KMS workload tokenUse disposable keys to verify a short-lived workload token, rehearse a planned signing-key rotation and check what happens when you revoke a workload.
- Check who can use an AWS KMS keyUse a test account and key to confirm which AWS roles can perform a particular operation and which roles can change the key policy.
- Propose a Safe transaction from a WalletConnect appFollow a test transaction from a wallet app to the Safe queue and see where owners review and confirm it.
- Approve an Ethereum test message with WalletConnectConnect an Ethereum test account, review the exact message on your phone, and verify the signature in the app that requested it.
- Sign a Bitcoin test payment with one keySign a payment on Bitcoin Core's local test network and compare the intended recipient, change and fee with what KeySigner shows before you approve.
- Test a shared Bitcoin payment that needs two keysRehearse a two-of-three payment on Bitcoin Core's local test network. Check that one signature falls short and that a second member's signature completes the payment.
- Test importing codes from a password managerUse a test account to check whether the KeySigner macOS authenticator can copy a time-based sign-in code from a 1Password 1PUX, KeePass XML or compatible KeePassXC XML export.
- Approve an Ethereum request from Google ChromeShare one test Ethereum account with a website and review a signing request on your phone.
- Rehearse a two-owner approval in SafePropose a test payment with one KeySigner owner, confirm it with a second owner and verify what the Safe actually executed.
- Approve an Ethereum request from FirefoxLoad the KeySigner development add-on in Firefox, share one Ethereum test account and verify a message signature.
- Send an Ethereum test token with KeySignerRehearse an ERC-20 transfer on an Ethereum test network and verify the exact amount that reached the recipient.
- Check an ENS recipient before sending EthereumRehearse an ETH transfer to a .eth name and compare the resolved address with the recipient shown in KeySigner before you approve.
- Recover a KeePassXC key fileRestore a test database key file from an encrypted KeySigner backup and confirm that it still opens KeePassXC.
- Verify a Solana transfer with KeySignerCheck the recipient, amount and signer of one SOL transfer with KeySigner’s local developer library.
- Simulate a Solana transfer locallyPreview the recipient and amount of a SOL transfer in a local Solana runtime. The exercise uses generated test keys and an in-memory balance.
- Rehearse a Squads approval thresholdCheck that a disposable 2-of-3 Squad needs two independent approvals before a vault transfer can be executed.
- Test an Ethereum network in your browserAdd a local Ethereum test network in Chrome or Firefox, review the network details in KeySigner, and switch between saved networks without signing a transaction.
- Import time-based codes from Google AuthenticatorCopy a test account’s time-based sign-in code into KeySigner, then check that the original service accepts a fresh code.
- 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.
- Check authenticator app policiesSee where to check whether Okta, Microsoft Entra ID, Google Workspace, or JumpCloud allows time-based authenticator codes for a test account.
- 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.
- Check who can merge a code changeFind the review decision for a specific revision and check what allows it to land in Bitbucket Cloud, Azure Repos, Gerrit or SourceHut.
- Test an approval gate before a releaseCheck which account can approve a test release and whether that approval lets the next job run in CircleCI, Buildkite, Jenkins or GitLab CI/CD.
- Check a trusted publisher on crates.io or NuGetTrace an existing package version back to its publishing workflow. These examples use GitHub Actions and the registry's trusted publishing settings.
- Check who can access a cloud resourceTrace a test identity's access to a resource in Google Cloud, Azure, Kubernetes, OpenStack or Hetzner Cloud. Use the same read action to check the effect of removing a test grant.
- Check when a token or certificate stops workingTest how HashiCorp Vault, Teleport and Smallstep end access. Check whether a live session stops, a fresh request fails or a certificate can no longer renew.
- Check what signs a Linux package or repositorySee which public key your package manager trusts for one source or package in Ubuntu, Debian or Red Hat Enterprise Linux.
- Verify who can open a test applicationAssign a test app to one account and check a second account stays outside the assignment. Compare the provider record with what each account can open.
- Check that a test account lands in the right appFollow a test account through the provider and into the intended app. Confirm the account, the app role and the administrator’s recovery path.
- Review what an employee test account can seeUse fictional employee records to check the limits of a workforce role. Verify what the account can view and whether a higher-privilege page stays restricted.
- Check which workforce data a connection can readCompare who can manage a workforce connection with the people and fields it can read. Check the result against fictional records.
- Check which school accounts get a test appUse two fictional accounts to check who can see a learning app and which roster records the provider shares.
- Verify a detached file signatureCheck which key signed a sample file, then change one byte and confirm the same signature fails.
- Verify who signed a container imagePin a test image by digest and require the intended publisher before a build or deployment accepts it.
- Check an approved container image with NotationVerify the publisher with Notation and check that the same container image digest is the one your KeySigner release owners approved.
- Check an approved Docker Hub image digestCheck that Docker Hub serves the exact multi-platform image your KeySigner release owners approved. Practice with the public hello-world image without publishing or changing a tag.
- Test who can sign with a managed keySign a harmless message with a test key, verify the signature and check whether a second identity has signing access.
- Check a token’s spending allowanceFind the contract that could spend a test token, check the limit, and verify the allowance after you remove it.
- Inspect a wallet request before approvalDecode a sample order or transaction to see which assets, addresses and contract actions your wallet is being asked to approve.
- Retest an Ethereum site connection in Chrome or FirefoxAfter changing a browser profile, device or test account, confirm which site can request a signature and which account it can use.
- 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.
- Troubleshoot a package release approvalIf your GitHub Actions workflow already waits for KeySigner approval before publishing to npm, use the request ID to see where the release stopped and what you can safely retry.
- 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 retired credentials for Bitbucket, npm, and PyPIFind out which credentials stopped working, what replaces them, and how to check repository access or package publishing before changing a live workflow.
- 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.
- Check Keycloak access to Red Hat OpenShiftUse Red Hat’s OpenShift 4.21 documentation to rehearse direct authentication through Keycloak and confirm a test user’s project access.
- Check an approved package with CosignUse KeySigner to check the package archive your release owners approved. Use Cosign to verify which publisher signed those same bytes.
- 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 a KeySigner wallet connection in AaveShare a disposable Ethereum address with Aave, check which account the dashboard opens, then remove the site's access in KeySigner.
- Test a KeySigner wallet connection in CurveShare a test Ethereum address with Curve Swap, check the account in the app header, then remove Curve’s access in KeySigner.
- Check a KeySigner wallet connection in BalancerCheck which Ethereum address Balancer Portfolio sees, then remove the site’s access in KeySigner. Balancer began moving eligible pools to withdrawals only on October 30, 2026.
- Check KeySigner wallet discovery in Lido and CompoundCheck what each app’s wallet picker shows before you share an Ethereum address.
- Check if Uniswap detects KeySignerFind KeySigner in the Uniswap wallet picker before sharing an Ethereum address.
- Check if OpenSea detects KeySignerFind KeySigner in OpenSea’s wallet picker and review which wallet types OpenSea supports.
- Check an approved npm archive with OpenSSL or GnuPGCheck who signed an npm archive and whether it matches the exact bytes your release owners approved in KeySigner.
- Test Polygon Amoy with Tenderly and KeySignerUse Tenderly’s public RPC to add the Polygon Amoy testnet in KeySigner and read the latest block. The test needs no wallet account, API key, or transaction.
- Connect KeySigner to an Alchemy test networkAdd Alchemy’s public World Chain Sepolia endpoint in KeySigner for Chrome and read the latest testnet block without sharing a wallet account.
- Verify a signed RPM against a KeySigner approvalCheck that a signed RPM came from the expected publisher and matches the exact package your release owners approved in KeySigner.
- 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.
- Test a passkey in DuoUse a passkey for the second verification step on a Duo-protected test app. Check the policy, enroll the passkey and match the test attempt to the Duo log.