I have an app that fetches characters assets using ESI. It was working for a long time but today I started getting HTTP 401 error for all requests that require ESI scopes. I thought maybe my tokens are not valid anymore and I re-authenticated the characters and I still get the same error. I think there is an issue with ESI.
Hey! CCP turned off v1 SSO tokens today. So if your app is still using the old version, that might explain your issue. Note that the SSO server still returns v1 tokens, but ESI no longer accepts it.
For more details see this: Removal of v1 authentication tokens
I’m having the same problem. My authorized 3rd party app was also working for months before today. Right now I’m able to authenticate the characters, but any subsequent calls for wallet, etc fail with unauthorized. Confirmed in Postman and in my own scripts. Testing in ESI Swagger UI works though.
Literally use GEMINI, the LLM/ ia of google and ask him to do the JWT validation routin. I was in a hurry and geot the code 99% functionl an adapt quicky to full fill my needes. anyqye they need what are the plans with esi.
I wasn’t paying close enough attention to the upcoming changes.
Migrating to OAuth V2 was pretty simple:
Update your authentication and token refresh endpoints to:
/v2/oauth/authorize
/v2/oauth/token
You might also need to include a new State parameter.
Some more documentation here: Single Sign-On - EVE Developer Documentation
1 Like
Updating should be easy:
All I had to do was add “/v2” to both my authorization and request uri’s.
Then I re-authorize to get my new token and it all worked.
https://login.eveonline.com/oauth/…
to:
https://login.eveonline.com/v2/oauth/…
As for the “state” parameter, I left it like I had it, which was “evesso”.