Skip to content

Parse content type on userInfo Response to allow application/jwt;charset=UTF-8#479

Open
samuelwei wants to merge 2 commits into
jumbojett:masterfrom
samuelwei:SamuelWei-parse-content-type
Open

Parse content type on userInfo Response to allow application/jwt;charset=UTF-8#479
samuelwei wants to merge 2 commits into
jumbojett:masterfrom
samuelwei:SamuelWei-parse-content-type

Conversation

@samuelwei
Copy link
Copy Markdown
Contributor

@samuelwei samuelwei commented May 6, 2025

In the current implementation the content type of the userInfo Reponse must be exactly application/jwt for signed and/or encrypted responses. However the OpenID Connect certification system is using application/jwt;charset=UTF-8 - therefore the strict content type check fails, resulting in empty scopes.

This PR extracts the content type and ignores the charset, so that the parsing of signed and/or encrypted responses is working again.

List of common tasks a pull request require complete

  • Changelog entry is added or the pull request don't alter library's functionality

@DeepDiver1975
Copy link
Copy Markdown
Collaborator

Unit tests please. THX

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.

2 participants