Skip to content

Comments

Fix: only validate client secret for non-public clients#657

Merged
NathaelB merged 2 commits intomainfrom
612-incorrect-client-secret-validation-logic-in-password-grant
Jan 12, 2026
Merged

Fix: only validate client secret for non-public clients#657
NathaelB merged 2 commits intomainfrom
612-incorrect-client-secret-validation-logic-in-password-grant

Conversation

@jorisvilardell
Copy link
Contributor

This pull request updates the authentication logic to better handle public clients and client secret validation. The main change ensures that public clients are not required to provide a client secret, and secret validation is performed only for non-public clients.

Authentication logic improvements:

  • Updated the client authentication flow in core/src/domain/authentication/services.rs so that public clients are not required to provide a client secret, and secret validation is now conditional on the client not being public.

@jorisvilardell jorisvilardell linked an issue Jan 12, 2026 that may be closed by this pull request
Copy link
Member

@NathaelB NathaelB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@NathaelB NathaelB merged commit 280087c into main Jan 12, 2026
8 checks passed
@NathaelB NathaelB deleted the 612-incorrect-client-secret-validation-logic-in-password-grant branch January 12, 2026 13:37
NathaelB pushed a commit that referenced this pull request Jan 16, 2026
* Fix: only validate client secret for non-public clients

* Fix: Simplify client secret validation logic
NathaelB added a commit that referenced this pull request Jan 16, 2026
* feat: add ThemeProvider and user theme menu (#651)

* feat: invalid id token field instead embedded into access token (#652)

* feat: refactor token generation and support id_token

Add a new `IdTokenClaims` struct and a `TokenClaims` trait to abstract
over different token claim types. Modify `create_jwt` to optionally
generate an ID token if the `openid` scope is present. Update `JwtToken`
to accommodate an optional ID token.

* fix: refactor token creation to include ID token

* fix: return service account not found exception when service account not found (#611) (#631)

* fix: only validate client secret for non-public clients (#657)

* Fix: only validate client secret for non-public clients

* Fix: Simplify client secret validation logic

---------

Co-authored-by: Luis Daniel RUBIERA <[email protected]>
Co-authored-by: Joris VILARDELL <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect Client Secret Validation Logic in Password Grant

2 participants