You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
If Semaphore is hosted without a subpath such as https://semaphoreserver.local:9999/ then according to the config docs the relevant option for the setting web_host should not have a trailing slash and should be empty in the config.
When logging in via OIDC (and perhaps other OAuth mechanisms) a successful auth flow returns the user to https://https://semaphoreserver.local:9999/api/auth/oidc/oidcprovidername/ with a HTTP 404 error and fails to redirect them to the Semaphore UI. Navigating away from this page to a URL such as https://semaphoreserver.local:9999/project/1/history works, which shows that the user has logged in successfully.
Cause & Workaround
After changing the web_host config value to "/" and restarting Semaphore, the user is now properly redirected upon a successful auth flow. I am not sure if this has any other negative impacts.
This behaviour could potentially be the cause for issues #1434, #2659, and #2666👿.
Issue
Problem
If Semaphore is hosted without a subpath such as
https://semaphoreserver.local:9999/
then according to the config docs the relevant option for the settingweb_host
should not have a trailing slash and should be empty in the config.When logging in via OIDC (and perhaps other OAuth mechanisms) a successful auth flow returns the user to
https://https://semaphoreserver.local:9999/api/auth/oidc/oidcprovidername/
with a HTTP 404 error and fails to redirect them to the Semaphore UI. Navigating away from this page to a URL such ashttps://semaphoreserver.local:9999/project/1/history
works, which shows that the user has logged in successfully.Cause & Workaround
After changing the
web_host
config value to "/" and restarting Semaphore, the user is now properly redirected upon a successful auth flow. I am not sure if this has any other negative impacts.This behaviour could potentially be the cause for issues #1434, #2659, and #2666👿.
Impact
Web-Frontend (what users interact with), Web-Backend (APIs)
Installation method
Package
Database
BoltDB
Browser
Chrome
Semaphore Version
2.11.2-0e9490c-1735214524
Ansible Version
Logs & errors
No response
Manual installation - system information
OS: Debian
Reverse proxy: Nginx
Configuration
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: