CODEWITHSUNDEEP
azuremicrosoft-graph-api
Arun Killu
Arun Killu

Reputation: 14233

Microsoft graph api for getting userinfo giving error

After OpenID authentication with Microsoft Azure AD while system tries to get the user details with https://graph.microsoft.com/oidc/userinfo Microsoft server throws below error.

enter image description here

  << "x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"North Central US","Slice":"SliceC","Ring":"3","ScaleUnit":"003","RoleInstance":"AGSFE_IN_22","ADSiteName":"NCU"}}[\r][\n]"
  << "Duration: 1.2061[\r][\n]"
  << "Strict-Transport-Security: max-age=31536000[\r][\n]"
  << "Date: Mon, 06 May 2019 06:47:24 GMT[\r][\n]"
  << "[\r][\n]"
  << "102[\r][\n]"
  << "{[\r][\n]"
  << "  "error": {[\r][\n]"
  << "    "code": "InternalServerError",[\r][\n]"
  << "    "message": "Object reference not set to an instance of an object.",[\r][\n]"
  << "    "innerError": {[\r][\n]"
  << "      "request-id": "45bf81f5-bcf7-4661-b69b-48947bdd76fe",[\r][\n]"
  << "      "date": "2019-05-06T06:47:24"[\r][\n]"
  << "    }[\r][\n]"
  << "  }[\r][\n]"
  << "}[\r][\n]"

Upvotes: 0

Views: 562

Answers (2)

Frank Z
Frank Z

Reputation: 91

We are seeing literally thousands of errors like below when calling: https://graph.microsoft.com/oidc/userinfo

and it seems random based on which server receives the request.

HTTP/1.1 500 Internal Server Error Cache-Control: private Content-Type: application/json; charset=utf-8 request-id: 253ceb44-8a32-4335-97b2-b776dfb8f6b3 client-request-id: 253ceb44-8a32-4335-97b2-b776dfb8f6b3 x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"East US","Slice":"SliceC","Ring":"2","ScaleUnit":"000","RoleInstance":"AGSFE_IN_26","ADSiteName":"EUS"}} Duration: 1.283 Strict-Transport-Security: max-age=31536000 Date: Wed, 08 May 2019 13:53:53 GMT Content-Length: 258

{ "error": { "code": "InternalServerError", "message": "Object reference not set to an instance of an object.", "innerError": { "request-id": "253ceb44-8a32-4335-97b2-b776dfb8f6b3", "date": "2019-05-08T13:53:54" } } }

Is there a link where I can see when that fix has been deployed that's scheduled for Thursday(9th may 2019) morning PDT as this is greatly impacting our business?

Upvotes: 0

Arun Killu
Arun Killu

Reputation: 14233

I have some news from Microsoft engineering team. It seems that this was an internal change that impacts AAD tokens that hits some datacenters. They are preparing a hotfix that will be deployed Thursday(9th may 2019) morning PDT, so everything should be fixed by that time.

Upvotes: 1

Related Questions