Description
The AccessToken3LResponse TypeScript interface does not include token_type or id_token fields. When using the openid scope (as recommended by LinkedIn's OAuth 2.0 docs), the token exchange response includes both fields, but they are not typed in the SDK.
Impact
token_type is part of the OAuth 2.0 spec (RFC 6749) and is always returned — omitting it means users must cast to any or augment the typeid_token is returned when openid scope is requested — this is LinkedIn's recommended auth flow, so most users will encounter this gap
Suggested fix
Add token_type: string and id_token?: string to AccessToken3LResponse. See PR #41.
Description
The
AccessToken3LResponseTypeScript interface does not includetoken_typeorid_tokenfields. When using theopenidscope (as recommended by LinkedIn's OAuth 2.0 docs), the token exchange response includes both fields, but they are not typed in the SDK.Impact
token_typeis part of the OAuth 2.0 spec (RFC 6749) and is always returned — omitting it means users must cast toanyor augment the typeid_tokenis returned whenopenidscope is requested — this is LinkedIn's recommended auth flow, so most users will encounter this gapSuggested fix
Add
token_type: stringandid_token?: stringtoAccessToken3LResponse. See PR #41.