karpor
karpor copied to clipboard
Feature Request: Support for OIDC Integration
What would you like to be added?
I’m looking to integrate this project with an identity provider using OpenID Connect (OIDC) for improved authentication and authorization workflows using oauth2-proxy. Currently, there doesn’t appear to be built-in support for OIDC, which makes it challenging to securely manage identities in cloud-native or enterprise environments.
Why is this needed?
OpenID Connect (OIDC) has become a standard protocol for authenticating users in modern applications. Adding support for OIDC in this project would bring several key benefits:
- Standards-based Authentication: OIDC is a widely adopted industry standard built on OAuth 2.0, ensuring secure and interoperable authentication flows.
- Single Sign-On (SSO): Enables seamless SSO experiences across multiple systems using trusted identity providers like Google, Azure AD, Okta, and Keycloak.
- Security Improvements: Removes the need to store or manage passwords directly, reducing the risk of breaches and simplifying compliance.
- Cloud-native and Enterprise Readiness: Most cloud platforms and enterprise environments prefer or require OIDC for identity federation and access management.
- Better User Management: Leverages existing user identities and access controls from the organization’s IdP (Identity Provider), avoiding the need to manage users within the application.
Supporting OIDC would make this project more secure, scalable, and enterprise-friendly.