search

trifork / klg-docs

Public documentation for Gateway
0 stars 8 forks source link

Authorization error #41

Closed LindaLawton closed 2 years ago

LindaLawton commented 2 years ago

Is something wrong with the authorizaotn server we are getting a strange error we haven't seen before.

 {"error":"server_error","error_description":"Organization Id Lookup failed"}

Fails in test and my unit tests.

Update: logs are saying error has been since Thursday. Everything ran fin Wednesday we have had no changes.

@jkiddo 

StatusCode: 500, ReasonPhrase: 'Internal Server Error', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:
{
  Cache-Control: no-store
  Date: Fri, 17 Jun 2022 11:49:26 GMT
  Pragma: no-cache
  Referrer-Policy: no-referrer
  Server: istio-envoy
  Strict-Transport-Security: max-age=31536000; includeSubDomains
  x-b3-traceid: 312d8a07dec2d8d9894a0f3e0760893d
  X-Content-Type-Options: nosniff
  x-envoy-upstream-service-time: 82
  X-Frame-Options: SAMEORIGIN
  X-Request-ID: 2741ef8a-74da-92e4-94c7-9a9f225cacb5
  X-XSS-Protection: 1; mode=block
  Connection: keep-alive
  Content-Type: application/json
  Content-Length: 76
}
jkiddo commented 2 years ago

@LindaLawton we'll look into it. May I assume this concerns the test environment, correct?

LindaLawton commented 2 years ago

Yes test we run daily load to test.

As far as I know production endpoints aren't live until Tuesday so we haven't tried them.

please let me know I spent several hours yesterday trying to debug this. unexplained errors this close to release worry me.

let me know as soon as you have an answer and I will test it.

LindaLawton commented 2 years ago

@jkiddo do we have an update on this. My tests are still failing.

We are going to production this week and test is down. I cant verify my system with the authorization down, all my end to end tests are failing. You have me very nervous here. Was this a scheduled outage? Can we get an idea when it will be back up again?

nigtrifork commented 2 years ago

Hi @LindaLawton

We are working on this right now. It is an internal error. We will have this fixed as soon as we find the cause.

LindaLawton commented 2 years ago

@nigtrifork thanks so much for the update.

nigtrifork commented 2 years ago

Hi @LindaLawton

The issue should be resolved now. If you can verify that, I will close this issue.

LindaLawton commented 2 years ago

Looks like its back up and running. Thanks.