Skip to content

Feat: add token_type and id_token to AccessToken3LResponse#41

Open
ZLeventer wants to merge 1 commit intolinkedin-developers:masterfrom
ZLeventer:feat/openid-token-types
Open

Feat: add token_type and id_token to AccessToken3LResponse#41
ZLeventer wants to merge 1 commit intolinkedin-developers:masterfrom
ZLeventer:feat/openid-token-types

Conversation

@ZLeventer
Copy link
Copy Markdown

Summary

  • Fixes Add the types for id_token and token_type for openid scope #32AccessToken3LResponse was missing token_type and id_token fields returned when using OpenID Connect scopes
  • Added two optional fields:
    • token_type?: string — the token type (e.g. "Bearer")
    • id_token?: string — JWT containing user identity claims (returned with openid scope)
  • Both are optional since they're only present in OpenID Connect flows

Test plan

  • Exchange an auth code using the openid scope and verify token_type and id_token are present in the response
  • Exchange an auth code without openid scope and verify no type errors (fields are optional)

When using the OpenID Connect scope, LinkedIn's OAuth token endpoint
returns id_token (JWT with identity claims) and token_type (e.g.
"Bearer") fields that were missing from the type definition.

Fixes linkedin-developers#32

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant