-
Notifications
You must be signed in to change notification settings - Fork 27
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
Access to 'GET /auth/currentCredential' route #20
Comments
bhubr
changed the title
Access to
Access to Jul 11, 2017
/auth/currentCredential
seems protected./auth/currentCredential
seems impossible.
bhubr
changed the title
Access to
Access to 'GET /auth/currentCredential' route
Jul 11, 2017
/auth/currentCredential
seems impossible.
Yes it should indeed. |
+1 |
Open
I made a PR for this #28 |
Hello, same pb... |
This i still an issue, #28 don't seems to be merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there from Toulouse ;).
I just started playing around with the Node API wrapper. I got my consumer key and validated it online.
Then I wanted to access
GET /auth/currentCredential
route and got the following response:Now I noticed that path check for setting the
X-Ovh-Consumer
header which obviously returnsfalse
for a request to any/auth/*
route. I think that it is the culprit, as commenting out the check, for test purposes, seemed to work, and I got my expected response:Checking out the code for the PHP, there doesn't seem to be such a condition for setting the Consumer and Signature headers. Shouldn't the check on path be more specific? Or am I getting something wrong?
The text was updated successfully, but these errors were encountered: