Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for GitLab authentication #266

Closed
wants to merge 1 commit into from

Conversation

ant8e
Copy link

@ant8e ant8e commented Nov 4, 2021

If the Ivy credential's realm contains the string "gitlab-private-token"
a Private-Token HTTP header with the value of the password is used instead
of the default basic authentication.

Should fix #241

If the Ivy credential's realm contains the string "gitlab-private-token"
a Private-Token HTTP header with the value of the password is used instead
of the default basic authentication.
@rtimush
Copy link
Owner

rtimush commented Nov 4, 2021

Thank you for your contribution! Do I understand it correctly that the gitlab-private-token realm doesn't come from the GitLab itself, but is just a convention?

@ant8e
Copy link
Author

ant8e commented Nov 5, 2021 via email

@rtimush
Copy link
Owner

rtimush commented Dec 5, 2021

Hi @ant8e. Sorry for a long delay. This change requires an additional configuration of the builds, which I'd like to avoid.
I've been thinking about an alternative way that reads the csrConfiguration setting, and I think I finally figured out a way to do it, while keeping compatibility with the older sbt versions (#276).

@rtimush rtimush closed this Dec 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Can't update from GitLab package repository
2 participants