So i’ve been working on a script using ESI SSO to pull killmails for a corpID. After a bit of frustrating trial and error I finally got the request to process. However now it is giving me a new problem. SSO Error 400. HTTP 403.
I did a little playing around with this in multiple ways. First made sure the corpID is being properly transmitted. Verified that I have and am sending the correct refresh token. And then plugged the data in manually on the EVE Swagger interface site to test if the problem was in the coding.
I am still getting the same error codes plugging into the EVE Swagger Interface manually. So for now i’m hesitant to say the problem is with my code.
Response Body
{
"error": "Invalid token: SO1AfjISUuhL6CnO...",
"sso_status": 400
}
Response Code
403
Response Headers
{
"strict-transport-security": "max-age=31536000",
"via": "1.1 google",
"status": "403",
"alt-svc": "clear",
"content-length": "66",
"x-esi-error-limit-remain": "100",
"last-modified": "Thu, 14 Sep 2017 04:00:48 UTC",
"date": "Thu, 14 Sep 2017 04:00:48 GMT",
"x-esi-error-limit-reset": "12",
"access-control-max-age": "600",
"access-control-allow-methods": "GET,OPTIONS",
"content-type": "application/json",
"access-control-allow-origin": "*",
"access-control-expose-headers": "Content-Type,Warning",
"cache-control": "private",
"access-control-allow-credentials": "true",
"access-control-allow-headers": "Content-Type,Authorization,X-User-Agent",
"expires": "Thu, 14 Sep 2017 04:01:18 UTC"
}
After seeing this I did consider that the scopes requested might be the issue. So I went back and verified both corp killmail and character killmail for ESI were selected (not the crest).
Any ideas or have I pretty much touched everything?