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.

Sign up for GitHub

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

Jump to bottom

private repositories from custom gitlab pulled without auth ( fails with 401) #158

Closed
bash-stack opened this issue May 19, 2020 · 2 comments · Fixed by #162
Closed

private repositories from custom gitlab pulled without auth ( fails with 401) #158

bash-stack opened this issue May 19, 2020 · 2 comments · Fixed by #162
Assignees
@karniv00l
Labels
bug Something isn't working
Milestone
0.3.0

Comments

@bash-stack
Copy link
Contributor

bash-stack commented May 19, 2020 •
edited
Loading

When trying to add a package from own gitlab :

  • the names of the repositories are listed (API)
  • but when repman tries to sync , it requests "upload-package" , without user credentials ( aka anonymous pull)
    Gitlab Response is 401

→ using a git https://username:token@gitlab.instance:123/path/to/repo.git URL as workaround

GitLab Log Output

 Parameters: {"service"=>"git-upload-pack", "namespace_id"=>"mygroup", "repository_id"=>"hereistherepo.git"}
Filter chain halted as :authenticate_user rendered or redirected
Completed 401 Unauthorized in 23ms
@akondas
Copy link
Member

akondas commented May 19, 2020

Yes, it is a bug in ComposerPackageSynchronizer, for gitlab packages authorization is hardcoded for gitlab.com. We will fix it asap 😉

@akondas akondas added the bug Something isn't working label May 19, 2020
@karniv00l karniv00l self-assigned this May 19, 2020
@karniv00l karniv00l added this to the 0.3.0 milestone May 19, 2020
@karniv00l karniv00l mentioned this issue May 19, 2020
Merged
@bash-stack bash-stack mentioned this issue May 19, 2020
Closed
@bash-stack
Copy link
Contributor Author

bash-stack commented May 19, 2020 •
edited
Loading

gets stuck now ( see #165 )

stuck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karniv00l karniv00l

Labels
bug Something isn't working
Projects
None yet
Milestone
0.3.0
Development

Successfully merging a pull request may close this issue.

Use gitlab custom url in ComposerPackageSynchronizer karniv00l/repman
3 participants
@karniv00l @akondas @bash-stack