Semaphore v2.17 introduces new features and improvements for infrastructure automation and DevOps teams. This release focuses on enhancing developer experience and streamlining infrastructure-as-code workflows.

Key Features Overview

Features

Custom issuer name in TOTP app

Semaphore v2.17 introduces a new option to customize the issuer name displayed in TOTP (Time-based One-Time Password) authenticator apps.

Purpose:
The issuer name helps users identify which account in their authenticator app belongs to Semaphore, especially useful when managing accounts from multiple organizations or environments.

How to Configure:

You can set the issuer name in two ways:

  1. Environment Variable

    Set the environment variable SEMAPHORE_TOTP_ISSUER to your desired issuer name when starting Semaphore.

    Example (Docker Compose):

    environment:
      - SEMAPHORE_TOTP_ISSUER=MyCompany Semaphore
    

    Example (Standalone):

    SEMAPHORE_TOTP_ISSUER="MyCompany Semaphore" ./semaphore server
    
  2. Configuration File

    In your config.json file, set the following option inside the auth section:

    {
      "auth": {
        "totp": {
          "issuer": "MyCompany Semaphore"
        }
      }
    }
    

Precedence:
If both the environment variable and the config file option are set, the environment variable (SEMAPHORE_TOTP_ISSUER) takes precedence.

Default Value:
If not set, the default issuer name will be Semaphore.

Result:
When users add their Semaphore TOTP account to an authenticator app, the selected issuer name will appear, making it easier to distinguish between multiple accounts.

For full details on all available environment variables, see the installation environment variable documentation.

New Feature 2

Detailed description of the second new feature. This section should include:

Enhanced User Interface

Description of UI improvements and enhancements:

Bug Fixes and Improvements

Breaking Changes

Note: List any breaking changes that users need to be aware of when upgrading.

Upgrade Instructions

To upgrade to Semaphore v2.17, follow the standard upgrade process:

  1. Stop your current Semaphore instance
  2. Update to the new version using your preferred installation method
  3. Restart Semaphore
  4. Verify the upgrade was successful

For detailed upgrade instructions, see the installation documentation.

What’s Next

We continue to focus on improving the infrastructure automation experience. Upcoming features include:

Thank you for using Semaphore! As always, we welcome your feedback and contributions.