You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But there are several things that may need a bit more thinking.
passport-gitlab2 gives node server power to use oauth2. But actually, static sites are directly backed by NGINX. NGINX Plus seems to support oauth2 (JWT Authentication) but it's not free.
oauth2_proxy is a powerful proxy but it is a little bit heavy to integrate (too many configurable things to expose). I think it may be better to introduce oauth2_proxy in README as an advanced option to provide GitLab oauth2 and even SSL ( ssl? #6 ) support.
It's hard to say that giving everyone who has access to GitLab the key to a locked doc is sufficient. It may be enough until GCP is able to give freedom to grant a group of people access to some site and another group of people access to some other sites.
Integrating passport-gitlab2 and using GitLab as Authentication provider would allow to build authenticated docs access.
The text was updated successfully, but these errors were encountered: