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
In forward-auth scenario either a custom x-forwarded-username header can be used (which is injected by the forward-auth mechanism), or a basic http authentication could be used (credentials are injected by the forward-auth mechannism).
Backrest seems to use bearer authentication which would not work with Authentik.
So either supporting basic auth or defining header with the username would be great addition to support SSO forward-auth.
The text was updated successfully, but these errors were encountered:
Sgtm, this can be supported by backrest. Happy to accept a PR if that’s something you’re interested in. I probably lean a bit in the direction of adding a basic auth mode (as opposed to bearer) mode.
Janhouse
added a commit
to Janhouse/backrest
that referenced
this issue
Feb 24, 2024
Would be great if basic http authentication could be used to authenticate users.
With SSO systems like Authentik you can use forward-auth to delegate authentication to the SSO system.
It can then send custom headers to the application which can use those headers to authenticate as a specific user.
In forward-auth scenario either a custom
x-forwarded-username
header can be used (which is injected by the forward-auth mechanism), or a basic http authentication could be used (credentials are injected by the forward-auth mechannism).Backrest seems to use bearer authentication which would not work with Authentik.
So either supporting basic auth or defining header with the username would be great addition to support SSO forward-auth.
The text was updated successfully, but these errors were encountered: