bug: Connector's Id token is invalid

[shreythakkar11]

Describe the bug

I wanted to add sign in with linkedin option in the authentication flow. There wasn't a direct option available for linkedin so I used the openid-connect (OIDC) option. I provided the jwks-uri as:

{
  "jwksUri": "https://www.linkedin.com/oauth/openid/jwks"
}

Authorization endpoint: https://www.linkedin.com/oauth/v2/authorization
Token endpoint: https://www.linkedin.com/oauth/v2/accessToken
Scope: openid profile email
Token Endpoint Auth Method: client_secret_post
Sync profile information: Only sync at sign-up

I do get the option of linkedin signin and even I am redirected to its authentication as well. After the authentication is done it redirects me to my sign in page and gives error as: The connector's id token is invalid.

And in the network tab, PATCH /api/interaction/identifiers API gives 401 with error response:

{
    "message": "The connector's id token is invalid.",
    "code": "connector.social_invalid_id_token",
    "data": {
        "issues": [
            {
                "code": "invalid_type",
                "expected": "boolean",
                "received": "string",
                "path": [
                    "email_verified"
                ],
                "message": "Expected boolean, received string"
            }
        ],
        "name": "ZodError"
    },
    "details": "Error in key path \"email_verified\": (invalid_type) Expected boolean but received string."
}

Expected behavior

The sign in through linkedin should be successful with no error alert.

How to reproduce?

Add the linkedin social connector for successful signing in with linkedin.

Context

I am running the logto app in my local system through the docker-compose

• Logto Cloud
• Self-hosted, Logto version =
  • Container (Docker image)
  • Raw Node.js

Screenshots

[xiaoyijun]

Hi @shreythakkar11 , thanks for your feedback.
It seems that the email_verified field data form the Linkedin is a string type, but in the Logto side, it needs a boolean type.
We will have a detailed investigation into this issue. However, you are also welcome to contribute code to help fix it.