Skip to content

fix: Validate JWT key length for HS256 compatibility - #188

Merged
CarlSchwan merged 1 commit into
masterfrom
fix/gss-jwt-key-length-error
Jul 6, 2026
Merged

fix: Validate JWT key length for HS256 compatibility#188
CarlSchwan merged 1 commit into
masterfrom
fix/gss-jwt-key-length-error

Conversation

@nfebe

@nfebe nfebe commented Mar 12, 2026

Copy link
Copy Markdown
Contributor

The HS256 algorithm requires a minimum key of 32 bytes per RFC 7518. firebase/php-jwt v7 (used by user_oidc) enforces this, while v6 (used by GSS) does not, causing silent JWT decode failures during OIDC logout delegation from slave to master.

Added key length validation with clear error logging in both Master and Slave, and updated README to document the requirement.

@CarlSchwan
CarlSchwan force-pushed the fix/gss-jwt-key-length-error branch from 5664e7b to 0a556ad Compare July 6, 2026 12:03
The HS256 algorithm requires a minimum key of 32 bytes per RFC 7518.
firebase/php-jwt v7 (used by user_oidc) enforces this, while v6
(used by GSS) does not, causing silent JWT decode failures during
OIDC logout delegation from slave to master.

Added key length validation with clear error logging in both
Master and Slave, and updated README to document the requirement.

Signed-off-by: nfebe <fenn25.fn@gmail.com>
@CarlSchwan
CarlSchwan force-pushed the fix/gss-jwt-key-length-error branch from 0a556ad to 2cc2ea8 Compare July 6, 2026 12:11
@CarlSchwan
CarlSchwan merged commit b414d6e into master Jul 6, 2026
38 checks passed
@CarlSchwan
CarlSchwan deleted the fix/gss-jwt-key-length-error branch July 6, 2026 13:33
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