Issue #5
0 up
0 down
Implement GITLAB HTTP_REMOTE_USER support correctly
Currently, we use omniauth to authenticate with HTTP_REMOTE_USER on Gitlab. So, Gitlab only authenticates the remote user when he/she tries to access a private page witch requires a logged user. There are many problems with that. Example:
- When you login by the first time on Colab and go to '/gitlab/public/projects' and access a public project you owner, you won't be able to edit it's settings and manage the project.
-
Status changed to closed