These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

CREST giving error 500 when trying to use refresh Token
Author
Previous Topic Next Topic
Cryten Jones
Advantage Inc
#1 - 2016-05-26 13:42:50 UTC  |  Edited by: Cryten Jones
Hi guys,

I am tearing my heir out here and was hoping that you can help.

Where I am up to:

I can get the user to login and collect the Authorization code
I can make a post request to 
login.eveonline.com/oauth/token
and gain the access token and refresh token
I can use the access token to walk the crest-tq.eve-online.com and view /decode branch etc (eg the token works)

However when I then try and use the refresh token to get a new access token it all goes wrong!

I am making a POST to login.eveonline.com/oauth/token


Authorization: Basic **exect same base64 encoded appkey used to get the first access token**

Post data = grant_type=refresh_token&refresh_token= **refresh Token got with the access token above**


Every time I get something like: Internal server error. Error ref: eadc77f9-9aa3-4f1f-9751-e62e9c46e857



Please tell me it's something stupid.. I just can't see it because I have been looking at it too long !
Mr Mac
Dark Goliath
#2 - 2016-05-26 16:04:17 UTC
500 is error on server. Try it later
Cryten Jones
Advantage Inc
#3 - 2016-05-26 17:15:45 UTC
Mr Mac wrote:
500 is error on server. Try it later



Yea.. it's been 20 hours now... thinking others would have noticed


Thanks though
Carbon Alabel
Gemini Talon
The Curatores Veritatis Auxiliary
#4 - 2016-05-26 18:37:39 UTC  |  Edited by: Carbon Alabel
Make sure you are sending the correct Content-Type header, in your case:
Content-Type: application/x-www-form-urlencoded

Also, make sure the character in question isn't docked in a citadel. Most citadel related bugs have been fixed, but they still make some things break from time to time.
If it's still not working, post the exact code you are using here. Might be an obscure feature of the library you are using breaking things.
Cryten Jones
Advantage Inc
#5 - 2016-05-26 20:51:14 UTC
Carbon Alabel wrote:
Make sure you are sending the correct Content-Type header, in your case:
Content-Type: application/x-www-form-urlencoded

Also, make sure the character in question isn't docked in a citadel. Most citadel related bugs have been fixed, but they still make some things break from time to time.
If it's still not working, post the exact code you are using here. Might be an obscure feature of the library you are using breaking things.



Thanks for the reply.

I do have that header yes, I was struggling to get the forum to let me post "code" and forgot to put it back in after working out it was the angle brackets !


As for library.. Writing my own BUT I am getting this something called Advanced REST client that just lets you build and send the requests.
Cryten Jones
Advantage Inc
#6 - 2016-05-27 16:57:58 UTC
Fixed it..

For those googling later for something like this I had managed to call the same scope twice on the initial post to /authorization

Interesting that it gives a valid access Token but an Invalid Refresh Token but there you have it

-CJ