You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: