8000 Use MAC terminology for client secret JWT algorithms by palasht75 · Pull Request #48988 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Use MAC terminology for client secret JWT algorithms - #48988

Closed
palasht75 wants to merge 1 commit into
keycloak:mainfrom
palasht75:fix-client-secret-jwt-mac-label
Closed

palasht75 wants to merge 1 commit into
keycloak:mainfrom
palasht75:fix-client-secret-jwt-mac-label

Conversation

@palasht75
@palasht75 palasht75 commented May 8000 13, 2026 •
Copy link
Copy Markdown
Contributor

Summary

Updates the Admin Console wording for HMAC algorithms used with client_secret_jwt.

Previously, the Admin Console referred to HS256, HS384, and HS512 as "Signature algorithm" options in this context. This change uses MAC terminology for the HMAC-based client secret JWT authenticator while preserving signature terminology where it applies to actual signature algorithms.

Closes #38664.

Testing

Using Java 21 / the repository-required frontend tooling:

  • cd js && corepack pnpm install --prefer-offline --frozen-lockfile - PASS
  • cd js && corepack pnpm --fail-if-no-match --filter @keycloak/keycloak-admin-ui lint - PASS
  • cd js && corepack pnpm --fail-if-no-match --filter @keycloak/keycloak-admin-ui test - PASS
  • cd js && corepack pnpm --fail-if-no-match --filter @keycloak/keycloak-admin-ui build - PASS
  • bash -c "$(sed 's/\\r$//' mvnw)" ./mvnw spotless:check - PASS
  • cd js && corepack pnpm --fail-if-no-match --filter @keycloak/keycloak-admin-ui exec playwright install chromium - PASS
  • cd js && corepack pnpm --fail-if-no-match --filter @keycloak/keycloak-admin-ui test:integration -- test/clients/details.spec.ts --project=chromium - PASS
  • cd js && corepack pnpm --fail-if-no-match --filter @keycloak/keycloak-admin-ui test:integration -- test/clients/advanced.spec.ts --project=chromium - PASS

Risk

The change is scoped to Admin Console terminology for client authentication algorithm selection.

No supported algorithms, stored configuration values, API behavior, or client authentication behavior are changed.

@palasht75
palasht75 marked this pull request as ready for review May 14, 2026 12:58
@palasht75
palasht75 requested review from a team as code owners May 14, 2026 12:58
Closes keycloak#38664

Signed-off-by: Palash Thakur <117917450+palasht75@users.noreply.github.com>
@palasht75
palasht75 force-pushed the fix-client-secret-jwt-mac-label branch from e25af4c to a5d99f5 Compare May 14, 2026 18:28
@lhanusov
Copy link
Copy Markdown
Contributor

@palasht75 can you please rebase to the latest main?

@lhanusov lhanusov assigned lhanusov and unassigned lhanusov Oct 21, 2026
@mposolda mposolda self-assigned this Oct 23, 2026
@mposolda mposolda left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think that PR is not complete. If we accept this change, we should rather update it on all relevant places. At least, it may update also at least the documentation https://www.keycloak.org/docs/latest/server_admin/index.html#_client-credentials .

Another thing is, that we have lots of options on various places, which allow both asymmetric and symmetric algorithms. For example, client has various options like "ID Token signature algorithms" etc. I am not sure if tooltips of those should be updated as well or if we can keep them as they are? This may need additional review whether to update or keep those. For the inspiration, here is OIDC dynamic client registration specification (some of Keycloak client options are "mapped" to OIDC dynamic client registration options https://openid.net/specs/openid-connect-registration-1_0.html#ClientMetadata ).

@jimmychakkalakal
Copy link
Copy Markdown
Contributor

Thanks, @palasht75, for your contribution and for starting the work to clarify MAC terminology. I’m continuing the work separately and expanding the updates to other relevant algorithm settings and documentation, so I’m closing this PR.

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.

Console incorrectly refers to MAC algorithms as "Signature algorithm"

6 participants

0