Auth0 /userinfo endpoint is returning 200 with empty response body

We are trying to use auth0 and we are facing an issue with /userinfo endpoint.

request_url: https://{redacted-testing-domain}
“mode”: “header”,
“header_format”: “Bearer %s”,
“param_name”: “access_token”
“params”: {},
“headers”: {
“Authorization”: “[FILTERED]”

But the response returned by auth0 does not contain any user information.

“headers”: {
“date”: “Fri, 26 May 2023 17:22:07 GMT”,
“content-type”: “application/json; charset=utf-8”,
“content-length”: “2”,
“connection”: “keep-alive”,
“cf-ray”: “7cd7b2cd7e5f387d-IAD”,
“cf-cache-status”: “DYNAMIC”,
“access-control-allow-origin”: “*”,
“cache-control”: “private, no-store, no-cache, must-revalidate, post-check=0, pre-check=0, no-transform”,
“etag”: “W/"2-vyGp6PvFo4RvsFtPoIWeCReyIC8"”,
“set-cookie”: “[FILTERED]”,
“strict-transport-security”: “max-age=31536000”,
“vary”: “Origin, Accept-Encoding”,
“access-control-allow-credentials”: “false”,
“access-control-expose-headers”: “X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset”,
“ot-baggage-auth0-request-id”: “f597e54146adc55d6e6b33b00960e225”,
“ot-tracer-sampled”: “true”,
“ot-tracer-spanid”: “6fcd1b627c1d7d14”,
“ot-tracer-traceid”: “6e6b33b00960e225”,
“traceparent”: “00-f597e54146adc55d6e6b33b00960e225-6fcd1b627c1d7d14-01”,
“tracestate”: “auth0-request-id=f597e54146adc55d6e6b33b00960e225,auth0=true”,
“x-auth0-requestid”: “384c48717d3230b10853”,
“x-content-type-options”: “nosniff”,
“x-ratelimit-limit”: “10”,
“x-ratelimit-remaining”: “9”,
“x-ratelimit-reset”: “1685121740”,
“server”: “cloudflare”,
“alt-svc”: “h3=":443"; ma=86400”
“raw_body”: “{}”,
“status”: 200

Scope is set to open profile email on auth0 authentication > social connection established.

What could be the possible reason? As there is no error in the http response (raw_body is {}), it’s difficult to identify the root cause to get it fixed.

Any suggestions / help is appreciated.

Can you confirm if you’re setting the scope to openid profile email instead of open profile email?

Yes, that was the issue. Not sure why but the value of scope was being set as read which causing the response to not contain desired attributes (maybe something related to our implementation)

Fixed by setting it to openid profile email and it fixed the issue.

1 Like

Perfect glad to hear that and thanks for sharing it with the rest of community!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.