Why to provide login/password when accessing GitLab with OAuth?
Completed
Following the documentation I manually created a project and successfully added a OAuth connection to our local GitLab server. When I want to create a build configuration now, I can choose one of the GitLab repositories. But when trying to proceed I get the error message "List remote refs failed: org.eclipse.jgit.errors.TransportException: https://our-git-server/foo/bar.git: not authorized". If I am not authorized, why can TeamCity get the URLs of the hosted repositories? And how can I get authorized? Providing username and password doesn't make sense for an OAuth based API access, does it? Or am I missing something?
Please sign in to leave a comment.
I have just clarified the details on how this integration works with devs. Application credentials allow to get a list of projects on GitLab side. However, in order to access repository data (for instance, during build configuration creation based on GitLab data) user authorization is required which is possible either through access token or login/password pair. While application credentials allow to retrieve access token, this is not supported as of now.
I`ve created feature request for user auth via application oAuth which you can track at https://youtrack.jetbrains.com/issue/TW-65219.