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

Implement oidc client functionality #185

Open
dadrus opened this issue Aug 17, 2022 · 0 comments
Open

Implement oidc client functionality #185

dadrus opened this issue Aug 17, 2022 · 0 comments
Labels
feature Used for new features
Milestone

Comments

@dadrus
Copy link
Owner

dadrus commented Aug 17, 2022

This would allow usage of heimdall without additional infrastructure components, like oauth2-proxy or lua-resty-openidc in environments where the oidc protocol is "misused" in a sense, that the oidc client and the resource server/relying party build the same application and oidc is used to get information about the authenticated user only, so only the id token is relevant.

In such 1st party scenarios, an auth proxy is used to drive the authorization code grant flow if no authentication information is present in the downstream request and ensures the user is authenticated. Currently, heimdall does only support the second part (and actually goes far beyond it)

Having that functionality in place would make heimdall a full fledged identity aware proxy

Requires #97

The plan is to implement OAuth for browser-based apps.

@dadrus dadrus added the feature Used for new features label Aug 17, 2022
@dadrus dadrus added this to the Future milestone Aug 17, 2022
@dadrus dadrus changed the title Implement oauth2 client functionality Implement oidc relying party functionality Aug 18, 2022
@dadrus dadrus changed the title Implement oidc relying party functionality Implement oauth2 client functionality Oct 27, 2022
@dadrus dadrus changed the title Implement oauth2 client functionality Implement oidc client functionality Oct 27, 2022
@dadrus dadrus modified the milestones: Future, v0.7.0-alpha Dec 20, 2022
@dadrus dadrus modified the milestones: v0.13.0-alpha, v0.14.0-alpha Nov 15, 2023
@dadrus dadrus modified the milestones: v0.14.0-alpha, next Jan 3, 2024
@dadrus dadrus modified the milestones: next, Future Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Used for new features
Projects
None yet
Development

No branches or pull requests

1 participant