Skip to content

Enhance OIDC Authentication: Support Dynamic Redirect URLs, Authentication State in Cookies, and Bearer Token Handling #166

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

Open
modoulo opened this issue Feb 13, 2025 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@modoulo
Copy link

modoulo commented Feb 13, 2025

Issue Description:

Currently, the OIDC authentication flow is limited due to a fixed redirectURL, preventing dynamic redirection for multiple applications. Additionally, applications without frontend authentication logic struggle to persist authentication state, and there is no support for Bearer tokens in HTTP headers.

Proposed Solution:

1. Support Multiple Applications with Dynamic Redirects:

Introduce a new configuration field, AuthorizedRedirectDomains []string, allowing users to define a list of authorized domains.
If an incoming request matches one of these domains, the appropriate redirectURL will be applied dynamically.

2. Persist Authentication State in Cookies:

Store authentication state in cookies to enable OIDC authentication for frontend applications without requiring custom authentication logic.

3. Support Bearer Tokens in Headers:

Allow authentication via Bearer tokens in HTTP headers, enabling backend services and microservices to authenticate requests without requiring cookie-based sessions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant