You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Sandor Molnar (Jira)" <ji...@apache.org> on 2021/01/08 08:30:00 UTC
[jira] [Created] (KNOX-2527) Support HMAC signature/verification in
JWT tokens
Sandor Molnar created KNOX-2527:
-----------------------------------
Summary: Support HMAC signature/verification in JWT tokens
Key: KNOX-2527
URL: https://issues.apache.org/jira/browse/KNOX-2527
Project: Apache Knox
Issue Type: New Feature
Components: KnoxSSO, Server
Affects Versions: 1.5.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 1.6.0
As of now, in {{DefaultTokenAuthorityService}}, the generated JWT token is signed by RSA (PKI). It would be beneficial to add support for HMAC as well so that token signature/verification would not require a keystore being set but using a secret stored via Knox's alias service. The recommended alias name is {{gateway.signing.hmac.secret}}
To support backward compatibility, the implementation should use HMAC signature/verification only if:
- the HMAC secret is configured via the alias service for the gateway
- there is no previously pre-configured {{gateway.signing.keystore.name}} which is a clear indication of end-user preference of using PKI signatures.
The default HMAC algorithm would be {{HS256}} (HMAC using SHA-256 hash algorithm), but this might be overridden by the already existing request parameter called {{knoxsso.token.sigalg}}. Other valid values are:
- {{HS384}}
- {{HS512}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)