# Test a Debian Salsa sign-in code

[Read this guide on KeySigner](https://keysigner.io/integrations/guides/test-a-debian-salsa-sign-in-code/)

Use an activated local Salsa account to confirm that a KeySigner code opens the intended Debian project in a fresh browser.

## Before you start

**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.

## Data and access

- **Shared or checked**. Salsa checks a fresh code for the activated account. The test confirms the displayed account and project permissions.
- **Check separately**. Check automation tokens, package upload authorization and archive signing independently of browser access.

## 1. Confirm the local Salsa account

Sign in at salsa.debian.org with an activated, email-verified test account you control. Note the username and an existing non-production project the account can read. Keep this original session open.

**Check.** The account is active on Salsa and opens the expected project.

## 2. Register the Salsa authenticator

In your Salsa profile, open Access, then Password and authentication. In the one-time password authenticator section, choose Register authenticator to display the QR code. In KeySigner, open Accounts and choose Add (+), then Sign-in codes and backup. Unlock Sign-in codes, choose Add account, and scan the setup QR code. Keep the QR code and setup key private.

![KeySigner for Mac shows options to scan a QR code, pick an image, or enter a setup link.](https://keysigner.io/integrations/guides/set-up-a-time-based-sign-in-code/keysigner-add-account.png)

Scan the setup code for your test account in KeySigner.

**Check.** KeySigner shows an entry for your Salsa account.

## 3. Confirm enrollment and keep the recovery codes

In KeySigner, choose Show code and complete the required approvals. Enter the displayed code before it changes. Complete the rest of Salsa’s enrollment form and choose Register with two-factor app. Download the recovery codes and store them separately.

**Check.** Salsa confirms enrollment and shows recovery codes.

## 4. Reopen the same project in a private browser

Open Salsa in a private browser using the same local username. When prompted by Salsa, enter a fresh KeySigner code. Confirm your avatar menu shows the original username and that the test project still opens.

**Check.** The private browser accepts a current code and shows the same account and project.

## Check your result

Record the Salsa host, account and project checked. Verify project membership, automation tokens, Debian package upload permissions, and archive signing separately.

### What we tested

**Tested on November 18, 2026.** In a local test, KeySigner imported a synthetic QR code and generated a code that matched an independent verifier. The hosted steps follow the provider’s published instructions. Confirm the hosted sign-in on your own test account.

[How to verify your setup](https://keysigner.io/integrations/verify-a-setup/)

## If you get stuck

### The expected Salsa account or project is missing

Check whether you opened a different GitLab instance or followed a linked external sign-in. Salsa requires an activated local account before you can link another identity. If the account and project match and the code expires, wait for a fresh code.

## Tools in this guide

- [Debian](https://keysigner.io/integrations/debian/)
  - [Verify the authenticity of Debian packages](https://www.debian.org/doc/manuals/debian-handbook/sect.package-authentication.en.html)
  - [Setup requirements](https://keysigner.io/integrations/setup-requirements/#debian)

## Setup instructions

- [Register an authenticator on Debian Salsa](https://salsa.debian.org/help/user/profile/account/two_factor_authentication.md#user-content-register-an-otp-authenticator)
- [Read Salsa account and activation requirements](https://wiki.debian.org/Salsa/Doc/#Users)
- [Check how Salsa links external accounts](https://wiki.debian.org/Salsa/FAQ)
- [Check a Debian package signature separately](https://keysigner.io/integrations/guides/check-linux-package-signatures/)
- [Review approval rules for a GitLab merge request](https://keysigner.io/integrations/guides/check-code-merge-approvals/#compare-approval-rules)

[More guides for this task](https://keysigner.io/integrations/tasks/set-up-sign-in-codes/)
