fix(connector): support string typed boolean ID token claims for OIDC connector

[darcyYe]

Summary

Add an optional acceptStringTypedBooleanClaims configuration to OidcConnectorConfig, with default value false.
For standard OIDC protocol, some claims such as email_verified and phone_verified are boolean-typed, but some providers may return them as string-typed. Enabling this option will convert string-typed boolean claims to boolean-typed, which provides better compatibility.
By enabling this configuration, the connector will accept string-typed boolean ID token claims, such as email_verified and phone_verified.

Testing

Covered by unit tests.

Checklist

• .changeset
• unit tests
• integration tests
• necessary TSDoc comments

[github-actions]

COMPARE TO master

Total Size Diff 📈 +4.77 KB

Diff by File

Name	Diff
.changeset/selfish-zoos-worry.md	📈 +611 Bytes
packages/connectors/connector-oidc/src/constant.ts	📈 +521 Bytes
packages/connectors/connector-oidc/src/index.ts	📈 +165 Bytes
packages/connectors/connector-oidc/src/types.test.ts	📈 +2.88 KB
packages/connectors/connector-oidc/src/types.ts	📈 +640 Bytes

[Copilot]

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

packages/connectors/connector-oidc/src/types.ts:34

• [nitpick] Consider shortening the name 'idTokenProfileStandardClaimsGuardAcceptingStringTypedBooleanClaims' for improved readability. For instance, a simpler name like 'idTokenClaimsGuardWithStringBooleans' might enhance clarity.

// Extend `idTokenProfileStandardClaimsGuard` by accepting string-typed boolean claims.

[simeng-li]

overall LGTM

[gao-sun]

lgtm on changeset