Based on the response in this GitHub issue, I suspect that the OIDC content provided by Logto may not fully comply with the standard.
When calling the userinfo endpoint with the openidconnect library, a parsing error occurred. This might suggest an issue with how the user information is being returned or formatted, potentially due to a deviation from the expected OpenID Connect standard in the response from Logto.
Expected behavior
This API should return a 200 status code along with JSON content compliant with the OIDC standard.
How to reproduce?
Retrieve user info using Rust’s openidconnect 3.5.0 and Logto Cloud.
Describe the bug
Based on the response in this GitHub issue, I suspect that the OIDC content provided by Logto may not fully comply with the standard.
When calling the userinfo endpoint with the openidconnect library, a parsing error occurred. This might suggest an issue with how the user information is being returned or formatted, potentially due to a deviation from the expected OpenID Connect standard in the response from Logto.
Expected behavior
This API should return a 200 status code along with JSON content compliant with the OIDC standard.
How to reproduce?
Retrieve user info using Rust’s openidconnect 3.5.0 and Logto Cloud.
Context