SOLVED How to authenticate in gitlab pipline?
-
Weird... it just keeps timing out for me when I try a docker push
-
Nevermind... got it working just fine.
-
@atrilahiji What did you do here? it seems this might be the source of the update issue which you mention in the other thread...
-
@girish oh I reinstalled making sure it used the apps user management. This was before my update issue
-
@girish The new update with the UI helped a lot. Reinstalled a version thats is standalone using proxyAuth and a version to integrate with GitLab. Works perfectly. I'll be doing some more extensive testing.
-
@atrilahiji Write up a post on it and we can get it into the docs I bet!
-
If I understand it correctly the gitlab integration makes gitlab the authority for docker registry submitting jwt tokens for authentication. To create these tokens you either make a access token deploy token or a personal token (especially if you are using 2fa) and one should be able to authenticate to the registry, correct?
I've tried all sorts of tokens and changing the docker-client in authproxy and nginxconfig without success.
Has anyone manged to get this working? ><
-
@caleno
I removed the auth token config from the docker registry and used the normal docker login cmd in my pipeline using my normal cloudron account name + an app password. -
I have token auth activated or at least configured and I can still log inn with Cloudron username and password + 2fa.
I'd like the token auth to work via Gitlab and maybe the case above points to a configuration issue.
I have to investigate further.
-
@caleno said in How to authenticate in gitlab pipline?:
I have token auth activated or at least configured and I can still log inn with Cloudron username and password + 2fa.
I'd like the token auth to work via Gitlab and maybe the case above points to a configuration issue.
I have to investigate further.
BTW. Maybe it is just working for the UI.
