planka_custom

Commit Graph

Author	SHA1	Message	Date
lebaudantoine	9aaaca1b8d	feat: Support OIDC signed UserInfo responses Some OIDC providers support signed UserInfo response, to enhance security. The OIDC client should be free to ask for the user info sgnature, however in certain situations (e.g egov applications) where security matters, the OIDC providers might chose to enforce this sugnature. Planka was not supported signed UserInfo response, which resulted in an misleading exception 'invalidCodeOrNonce'. Introduce the proper configurations to parametrize the OIDC client, and a dedicated exception to improve the developer experience. Specifications: "The UserInfo Claims MUST be returned as the members of a JSON object unless a signed or encrypted response was requested during Client Registration."	1 year ago
Maksim Eltyshev	40c04c35ff	ref: Refactoring	2 years ago

Author

SHA1

Message

Date

lebaudantoine

9aaaca1b8d

feat: Support OIDC signed UserInfo responses

Some OIDC providers support signed UserInfo response, to enhance
security. The OIDC client should be free to ask for the user info
sgnature, however in certain situations (e.g egov applications)
where security matters, the OIDC providers might chose to enforce
this sugnature.

Planka was not supported signed UserInfo response, which resulted
in an misleading exception 'invalidCodeOrNonce'.

Introduce the proper configurations to parametrize the OIDC client,
and a dedicated exception to improve the developer experience.

Specifications:

"The UserInfo Claims MUST be returned as the members of a JSON
object unless a signed or encrypted response was requested
during Client Registration."

Maksim Eltyshev

40c04c35ff

ref: Refactoring

2 Commits (9aaaca1b8d9c34f2587c361abeae7a13e3392331)