local-oidc-https-proxy

OIDC authentication fails locally because modern browsers reject session cookies without real TLS on localhost, causing infinite login loops. Configuring a secure HTTPS reverse proxy resolves this by providing valid HTTPS endpoints for browser-compatible cookie handling.

Configure an HTTPS reverse proxy for local OIDC by terminating TLS using the .NET development certificate and aligning the browser-facing origin with the application's transport layer. This setup validates transport protocols and ensures seamless authentication flows.

Keycloak requires TLS for local OIDC session cookies to ensure browser policy compliance. Without valid HTTPS endpoints, browsers reject cookies lacking Secure and SameSite=None attributes, breaking the local authentication process.

Yes, you can use a YARP proxy with the .NET development certificate to terminate TLS for local OIDC providers. This aligns external authority metadata with internal containerized services, ensuring seamless authentication flows.

The best way to fix infinite OIDC login loops is to configure a local reverse proxy that terminates TLS using a valid development certificate. This ensures IdP cookies are correctly marked as Secure and SameSite=None by aligning the transport layer.

OIDC session cookies are rejected on localhost due to the absence of real TLS. Modern browsers require HTTPS to properly set Secure and SameSite=None cookie attributes, which a local HTTPS reverse proxy provides.