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

401 errors with Fedora 3 using migrate_7x_claw #1624

Open
dannylamb opened this issue Sep 18, 2020 · 1 comment
Open

401 errors with Fedora 3 using migrate_7x_claw #1624

dannylamb opened this issue Sep 18, 2020 · 1 comment
Labels
Type: bug identifies a problem in the software with clear steps to reproduce

Comments

@dannylamb
Copy link
Contributor

Ran into this live debugging a migration with @martha

Despite having correct credentials in the configuration form and ensuring there is no deny-apim-if-not-localhost policy floating around, we were still getting 401'd when trying to access fedora. Using both the browser and curl was successful, but for some reason the migrate framework couldn't connect.

I don't think the issue is another xacml policy. Maybe it's just how guzzle is configured? This one's a headscratcher.

@ruebot
Copy link
Member

ruebot commented Sep 25, 2020

I was getting this a lot back pre-COVID when I was trying to test out migrate_7x_claw on a number of York collections. Had some Slack conversations with folks, and definitely walked away headscratching.

@kstapelfeldt kstapelfeldt added bug and removed wontfix labels Sep 9, 2021
@kstapelfeldt kstapelfeldt added Type: bug identifies a problem in the software with clear steps to reproduce and removed bug labels Sep 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: bug identifies a problem in the software with clear steps to reproduce
Projects
Development

No branches or pull requests

3 participants