How to stop auto-login using oauth2-proxy, but still refresh sessions when login endpoint was hit once and session exists

Viewed 25

I'm curious if ouath2-proxy in an K8S Istio setup can be configured such that login only happens for a host if a user manually requested it pressing a login button for example that redirects to /oauth/start.

My use case would be, having a publicly available site where if you login you'd get extra features. A forced login doesn't fit this case, and from reading the documentation I can't see how to stop it.

Another thing would be if the user clicked login, is there a way to keep the session fresh if the automatic part is disabled?

If ouath2-proxy doesn't fit, is there an alternative setup I could look into? Even ideas on how to split public / private hosts would be greatly appreciated.

0 Answers
Related