Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use OIDC/SAML backwards to pass valid jwt token/roles/user to other Oauth/SAML compatible apps protected by Caddy reverse proxy #323

Open
TedSheckler2021 opened this issue Mar 3, 2024 · 1 comment
Assignees
Labels
need triage question Further information is requested

Comments

@TedSheckler2021
Copy link

TedSheckler2021 commented Mar 3, 2024

Hi there

I know you can do OIDC/SAML as a forward auth provider, but I was wondering if caddy sec can pass a session backwards via OIDC/SAML

Im trying to avoid multple logins, just use the fantastic Caddy/Caddy Security login once (I know that's a Keycloak thing) .. I just like caddy because it's one stop shopping

It might be possible, I've successfully passed custom headers from the JWT token to automatically login certain compatible tools like cloudbeaver

https://github.com/dbeaver/cloudbeaver/wiki/Reverse-proxy-header-authentication

but most apps support OIDC/SAML .. and you can't just pass headers like that for a SSO.. ish behaviour without OIDC/SAML inbound as a forward_auth

Example apps, Superset/PGAdmin etc

I usually just disable the app accounts, and have users share one account, but ideally, id like to segregate them by caddy sec role, without the overhead of external Identity Provider (IdP) like Okta, Auth0

thanks in advance

@TedSheckler2021 TedSheckler2021 added need triage question Further information is requested labels Mar 3, 2024
@greenpau
Copy link
Owner

greenpau commented Mar 3, 2024

@TedSheckler2021 , please reach out to me on LinkedIn and let's have Google Meet to discuss it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need triage question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants