Credentials are ignored

[rabejens]

I set up a new Gitlab token with api access, then I created ~/.sbt/.gitlab.credentials like so:

realm=mygroup
host=my.company.com
user=Private-Token
password=REDACTED

In my build.sbt I have:

ThisBuild / useCoursier := false

credentials += Credentials(Path.userHome / ".sbt" / ".gitlab.credentials")
resolvers += "mygroup" at "https://my.company.com/api/v4/groups/420/-/packages/maven"

Now,

libraryDependencies += "com.company.my" %% "my-lib" % "1.2.3"

But it still can't find the package. It seems to ignore the credentials:

[warn] 	module not found: com.company.my#my-lib_2.12;1.2.3
[warn] ==== local: tried
[warn]   C:\Users\MyUsername\.ivy2\local\com.company.my\my-lib_2.12\1.2.3\ivys\ivy.xml
[warn] ==== public: tried
[warn]   https://repo1.maven.org/maven2/com/company/my/my-lib_2.12/1.2.3/my-lib_2.12-1.2.3.pom
[warn] ==== local-preloaded-ivy: tried
[warn]   C:\Users\MyUsername\.sbt\preloaded\com.company.my\my-lib_2.12\1.2.3\ivys\ivy.xml
[warn] ==== local-preloaded: tried
[warn]   file:/C:/Users/MyUsername/.sbt/preloaded/com/company/my/my-lib_2.12/1.2.3/my-lib_2.12-1.2.3.pom
[warn] ==== mygroup: tried
[warn]   https://my.company.com/api/v4/groups/420/-/packages/maven/com/company/my/my-lib_2.12/1.2.3/my-lib_2.12-1.2.3.pom

When I follow the link and log in to our company Gitlab previously, the POM is downloaded fine.

What is going wrong here? What am I missing?

When I set up a Maven project accessing this repo, everything works fine.

[mxndtr]

Similar problem.
sbt-1.6.2
scala-2.13.8

Works оnly with GitlabPlugin.autoImport.gitlabCredentials

[rabejens]

Even this does not work for me. I am using the correct realm, gitlab-maven, and still getting Not found.

Followup:

Not a solution but a workaround that works for our use cases.

Since we are running a Kubernetes Cluster on-prem, I simply installed a Sonatype Nexus there, which supports "pure Maven style" repositories, and registered a Gitlab Runner on this cluster. I then break up my CI job into multiple sub-jobs and where getting our own company code is needed, I use the runner on our cluster.

[Magnie]

I am running into the same issue at my company. I've tried the credentials file, I've tried putting the key directly into the code, different realms (gitlab and gitlab-maven), and they all end with "not found" errors.

[rabejens]

This really seems to be an Ivy issue, because when trying to get dependencies on the fly from within Apache Spark, I am hitting the same problems.

[hoop33]

I just hit this issue after upgrading from sbt 1.6.2 to 1.8.2. I checked the sbt manual, and everything looked the same for specifying credentials. On a whim, I tried:

ThisBuild / credentials += ...

instead of:

credentials += ...

And that worked. YMMV.

[rabejens]

No, this still doesn't work for me. There also doesn't seem to be any recent activity here...