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
-
Custom issuer name in TOTP app
You can now specify a custom issuer name when registering Semaphore with a TOTP (Time-based One-Time Password) authenticator app. This enables clearer identification of Semaphore accounts within authenticator apps, improving usability—especially for users managing multiple 2FA tokens.
Learn more » -
New Feature 2
Description of the second major feature introduced in this version.
Learn more » -
Enhanced User Interface
Improvements to the user interface for better usability and productivity.
Learn more »
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:
-
Environment Variable
Set the environment variable
SEMAPHORE_TOTP_ISSUERto your desired issuer name when starting Semaphore.Example (Docker Compose):
environment: - SEMAPHORE_TOTP_ISSUER=MyCompany SemaphoreExample (Standalone):
SEMAPHORE_TOTP_ISSUER="MyCompany Semaphore" ./semaphore server -
Configuration File
In your
config.jsonfile, set the following option inside theauthsection:{ "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:
- Key benefits and use cases
- How to use the feature
- Configuration examples if applicable
- Integration with existing workflows
Enhanced User Interface
Description of UI improvements and enhancements:
- Visual improvements
- Usability enhancements
- New interface elements
- Performance optimizations
Bug Fixes and Improvements
- Fixed issue with [specific functionality]
- Improved performance for [specific operations]
- Enhanced error handling and messaging
- Updated dependencies and security patches
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:
- Stop your current Semaphore instance
- Update to the new version using your preferred installation method
- Restart Semaphore
- 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:
- Future feature previews
- Roadmap items
- Community requests
Thank you for using Semaphore! As always, we welcome your feedback and contributions.