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
{{ message }}
This repository was archived by the owner on Mar 18, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 18, 2019. It is now read-only.
Authentication headers aren't being sent with coreapi 2.3.0, but 2.2.4 works #19
changed the title [-]Authentication headers aren't being sent[/-][+]Authentication headers aren't being sent with coreapi 2.3.0, but 2.2.4 works[/+]on May 22, 2017
I degraded coreapi to 2.2.4, and coreapi-cli is 1.0.6. But I still get error of "TypeError: init() missing 1 required positional argument: 'enum'". Any idea? Thanks.
coreapi-cli is using the deprecated credentials argument for HTTPTransport instead of auth. As you can see from the code here, coreapi 2.3.1 is ingesting that deprecated argument, but then doing nothing with it. This is why this library won't send auth headers anymore.
@blueyed Thanks! @tomchristie It would be awesome if you could have a look into this... atm any coreapi-generated doc will point to use the coreapi client and this is broken 📦
@bradleyglen Thanks, I can confirm that. With 2.2.4 I'm getting TypeError: __init__() missing 1 required positional argument: 'enum', and with a higher version (2.3.x) it just doesn't work. It adds credential, but does not authenticate. I've only tested it with coreapi credentials add 127.0.0.1 <username>:<password> --auth basic command.
The CLI doesn't seem to correctly use coreapi's authentication anymore with the latest coreapi libary.
If I use coreapi cli 1.0.6 and coreapi 2.0.0, the authentication header is being sent (Not my real creds or domain):
But if I switch to the latest coreapi 2.3.0, it doesn't get sent:
For the moment, I'm just reverting to coreapi 2.0.0 as a workaround.