fix(hermes): edge-redirect dashboard root to password-login#754
Merged
Conversation
Hermes basic-auth is password-only, so bare / redirects into /auth/login?provider=basic and 500s. Print the pretty dashboard host, edge-redirect Exact / → /auth/password-login on the dashboard HTTPRoute, document credentials, and smoke-check root + password-login in flow-04.
OisinKyne
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/500 via/auth/login?provider=basic(NotImplementedError: BasicAuthProvider is password-only)./→/auth/password-loginon the dashboard HTTPRoute only (agent API host unchanged).Dashboard: http://…plus usernameoboland password =obol agent auth <id>./api/status200 and protected API 401).docs/guides/hermes-dashboard-login.md, README + getting-started.Test plan
go test ./internal/hermes/ -count=1bash -n flows/flow-04-agent.shobol agent sync(or stack up) applies dashboard HTTPRoute redirectcurl -I http://obol-agent.obol.stack/→ 302 to/auth/password-loginobol+obol agent auth