error: invalid_client
Moderators: StaffingSupport, s.emmons, BullhornSupport
-
- User
- Posts: 28
- Joined: Sat Nov 17, 2012 12:06 am
error: invalid_client
I am attempting to get my access token using the Google Chrome extension Simple REST Client. I POST to the following URL https://auth.bullhornstaffing.com/oauth ... ent_secret] substituting my values with the placeholders in the query string and I get the following error in the response data:
{
"error" : "invalid_client",
"error_description" : "Client authentication failed."
}
Is anyone having any luck with this?
{
"error" : "invalid_client",
"error_description" : "Client authentication failed."
}
Is anyone having any luck with this?
Re: error: invalid_client
Hi enapoleone,
Good morning and thanks for your post. In order for me to properly assist and run some tests, can you please provide me your client ID?
Thanks,
Good morning and thanks for your post. In order for me to properly assist and run some tests, can you please provide me your client ID?
Thanks,
Ryan Knight
Principal Enterprise Support Analyst and Team Lead
B U L L H O R N
33-41 Farnsworth Street, 5th Floor, Boston, MA 02210
US Support: 617-478-9126
International Support: +1 617 478 9131
http://www.bullhorn.com
Principal Enterprise Support Analyst and Team Lead
B U L L H O R N
33-41 Farnsworth Street, 5th Floor, Boston, MA 02210
US Support: 617-478-9126
International Support: +1 617 478 9131
http://www.bullhorn.com
-
- User
- Posts: 28
- Joined: Sat Nov 17, 2012 12:06 am
Re: error: invalid_client
Hi Ryan,
My client ID is 408396f4-461d-4194-b39a-4e046089ccc9
Thanks in advanced
John
My client ID is 408396f4-461d-4194-b39a-4e046089ccc9
Thanks in advanced
John
Re: error: invalid_client
Hi John,
Everything seems to be configured correctly for your company in terms of the API key, client ID, and client secret. I am able to use the same URL that you are (https://auth.bullhornstaffing.com/oauth ... ent_secret]) and using an HTTP POST with the appropriate values.
This is working fine for me which returned the following JSON response, as I would expect (I've omitted the refresh token and access token for security reasons.)
Do you mind emailing me some more information (off the forums) so I can further troubleshoot? Please email the following to bullhornbuddy@gmail.com and REPLY back to this post to confirm you've sent the information:
What API username are you using?
What authorization code are you passing in the POST request (please provide a new one that is valid)? You may also send me the full URL.
What is the client secret you have on record?
I will respond back to your email and update this forum accordingly at a later point.
Everything seems to be configured correctly for your company in terms of the API key, client ID, and client secret. I am able to use the same URL that you are (https://auth.bullhornstaffing.com/oauth ... ent_secret]) and using an HTTP POST with the appropriate values.
This is working fine for me which returned the following JSON response, as I would expect (I've omitted the refresh token and access token for security reasons.)
Code: Select all
Returned the following JSON without issue:
Status:200 OK
Date: Fri, 28 Dec 2012 17:35:20 GMT
Transfer-Encoding: chunked
nnCoection: close
Pragma: no-cache
Server: Apache-Coyote/1.1
Content-Type: application/json;charset=UTF-8
Cache-Control: no-store
{
"access_token" : "REMOVED",
"token_type" : "Bearer",
"expires_in" : 600,
"refresh_token" : "REMOVED"
}
What API username are you using?
What authorization code are you passing in the POST request (please provide a new one that is valid)? You may also send me the full URL.
What is the client secret you have on record?
I will respond back to your email and update this forum accordingly at a later point.
Ryan Knight
Principal Enterprise Support Analyst and Team Lead
B U L L H O R N
33-41 Farnsworth Street, 5th Floor, Boston, MA 02210
US Support: 617-478-9126
International Support: +1 617 478 9131
http://www.bullhorn.com
Principal Enterprise Support Analyst and Team Lead
B U L L H O R N
33-41 Farnsworth Street, 5th Floor, Boston, MA 02210
US Support: 617-478-9126
International Support: +1 617 478 9131
http://www.bullhorn.com
-
- User
- Posts: 28
- Joined: Sat Nov 17, 2012 12:06 am
Re: error: invalid_client
Hi Ryan,
I've emailed the details that you requested.
Thanks again,
John
I've emailed the details that you requested.
Thanks again,
John
Re: error: invalid_client
Hi John,
Thanks for your patience. I received your email and the URL and values you used in your method to get the Auth code were fine...the client secret and client ID are exactly what I used to get the access token successfully. The only difference is the auth code portion (&code=[XXXXX]) - I used something different obviously. Have you tried getting another auth code and passing the new value to get the access token?
Thanks for your patience. I received your email and the URL and values you used in your method to get the Auth code were fine...the client secret and client ID are exactly what I used to get the access token successfully. The only difference is the auth code portion (&code=[XXXXX]) - I used something different obviously. Have you tried getting another auth code and passing the new value to get the access token?
Ryan Knight
Principal Enterprise Support Analyst and Team Lead
B U L L H O R N
33-41 Farnsworth Street, 5th Floor, Boston, MA 02210
US Support: 617-478-9126
International Support: +1 617 478 9131
http://www.bullhorn.com
Principal Enterprise Support Analyst and Team Lead
B U L L H O R N
33-41 Farnsworth Street, 5th Floor, Boston, MA 02210
US Support: 617-478-9126
International Support: +1 617 478 9131
http://www.bullhorn.com
-
- User
- Posts: 28
- Joined: Sat Nov 17, 2012 12:06 am
Re: error: invalid_client
Hi Ryan,
It's a very busy time of the year, I totally understand. Thank you for getting back to me.
I tried a couple of times to get a new auth code and always get the same result. Is what you used something totally different?
Thanks,
John
It's a very busy time of the year, I totally understand. Thank you for getting back to me.
I tried a couple of times to get a new auth code and always get the same result. Is what you used something totally different?
Thanks,
John
Re: error: invalid_client
Hi John,
Thanks and Happy New Year to you.
The fact that you continue to get the same response for the auth code seems to be the problem. You should get something different when you invoke the auth code URL: https://auth.bullhornstaffing.com/oauth ... _type=code
As an example, I just hit the URL three times with your API credentials and received the following responses:
?code=2%3Aac-8d3b0ff5-530b-4a56-93ed-b1de7c4c4b35
?code=2%3Aac-c3d026bd-fd9b-4c79-9132-5da13a361684
?code=2%3Aac-b4263558-a70c-492f-8909-dbeeff1dd4e1
My guess is that something is awry with your browser caching the auth code (assuming you are still doing it within the browser). Would you be able to try another browser or clearing your browser data to see if you get a different code on the response?
Please let me know.
Ryan
Thanks and Happy New Year to you.
The fact that you continue to get the same response for the auth code seems to be the problem. You should get something different when you invoke the auth code URL: https://auth.bullhornstaffing.com/oauth ... _type=code
As an example, I just hit the URL three times with your API credentials and received the following responses:
?code=2%3Aac-8d3b0ff5-530b-4a56-93ed-b1de7c4c4b35
?code=2%3Aac-c3d026bd-fd9b-4c79-9132-5da13a361684
?code=2%3Aac-b4263558-a70c-492f-8909-dbeeff1dd4e1
My guess is that something is awry with your browser caching the auth code (assuming you are still doing it within the browser). Would you be able to try another browser or clearing your browser data to see if you get a different code on the response?
Please let me know.
Ryan
Ryan Knight
Principal Enterprise Support Analyst and Team Lead
B U L L H O R N
33-41 Farnsworth Street, 5th Floor, Boston, MA 02210
US Support: 617-478-9126
International Support: +1 617 478 9131
http://www.bullhorn.com
Principal Enterprise Support Analyst and Team Lead
B U L L H O R N
33-41 Farnsworth Street, 5th Floor, Boston, MA 02210
US Support: 617-478-9126
International Support: +1 617 478 9131
http://www.bullhorn.com
-
- User
- Posts: 28
- Joined: Sat Nov 17, 2012 12:06 am
Re: error: invalid_client
Hi Ryan,
Yes, Happy New Year to you too!
I think I failed to communicate in my last post what was actually happening to me.
I do get a different Auth code every time I go to https://auth.bullhornstaffing.com/oauth ... irect_uri=[optional redirect_uri]. I just get the same result each time when I try to use the code to obtain an access token, "invalid_client".
Let me try to be a little more explicit about what I'm doing in case I'm just doing something completely wrong.
I open Simple REST Client (Chrome) take the below URL and substitute my values for the placeholders and put it in the URL field, select POST from the Method radio buttons and hit Send.
https://auth.bullhornstaffing.com/oauth ... ent_secret]
John
Yes, Happy New Year to you too!
I think I failed to communicate in my last post what was actually happening to me.
I do get a different Auth code every time I go to https://auth.bullhornstaffing.com/oauth ... irect_uri=[optional redirect_uri]. I just get the same result each time when I try to use the code to obtain an access token, "invalid_client".
Let me try to be a little more explicit about what I'm doing in case I'm just doing something completely wrong.
I open Simple REST Client (Chrome) take the below URL and substitute my values for the placeholders and put it in the URL field, select POST from the Method radio buttons and hit Send.
https://auth.bullhornstaffing.com/oauth ... ent_secret]
John
Re: error: invalid_client
Hi,
So I sent a reply via a ticket that came in, but wanted to post here as well. The invalid client error appears to have stemmed from a mistyped Client Secret. I provided the proper value on the ticket, but mainly the first T was being passed as lowercase versus Upper (correct).
Hope that helps!
So I sent a reply via a ticket that came in, but wanted to post here as well. The invalid client error appears to have stemmed from a mistyped Client Secret. I provided the proper value on the ticket, but mainly the first T was being passed as lowercase versus Upper (correct).
Hope that helps!
Re: error: invalid_client
Thanks c.choy.
John - my apologies for missing that the first time around. Let us know if you have any other issues.
John - my apologies for missing that the first time around. Let us know if you have any other issues.
Ryan Knight
Principal Enterprise Support Analyst and Team Lead
B U L L H O R N
33-41 Farnsworth Street, 5th Floor, Boston, MA 02210
US Support: 617-478-9126
International Support: +1 617 478 9131
http://www.bullhorn.com
Principal Enterprise Support Analyst and Team Lead
B U L L H O R N
33-41 Farnsworth Street, 5th Floor, Boston, MA 02210
US Support: 617-478-9126
International Support: +1 617 478 9131
http://www.bullhorn.com
-
- User
- Posts: 28
- Joined: Sat Nov 17, 2012 12:06 am
Re: error: invalid_client
c.choy, thank you for your assistance.
I haven't been forwarded your response to the ticket, however I believe that I understood what you meant and which character needed to be altered.
However, after renewing my auth_code I get the following error when trying to use it to obtain my access_token:
{
"error" : "invalid_grant",
"error_description" : "Mismatch redirect uri."
}
I haven't been forwarded your response to the ticket, however I believe that I understood what you meant and which character needed to be altered.
However, after renewing my auth_code I get the following error when trying to use it to obtain my access_token:
{
"error" : "invalid_grant",
"error_description" : "Mismatch redirect uri."
}
Re: error: invalid_client
I'll take a look, for now you can get around it by not passing the redirect_uri option (you'll have to go back a couple steps for that)
-
- User
- Posts: 28
- Joined: Sat Nov 17, 2012 12:06 am
Re: error: invalid_client
Omitting the redirect_uri from the the Auth Code step resolved this error.
Thank you Ryan and c.choy for your assistance.
I have a few more questions but will start a new thread for them.
Thank you Ryan and c.choy for your assistance.
I have a few more questions but will start a new thread for them.
Re: error: invalid_client
I'm having this issue as well.
Is there someone I can forward my API details to check if they're correct?
Regards
Is there someone I can forward my API details to check if they're correct?
Regards