[jira] [Created] (JAMES-4139) Optimize JWT key management
"Amichai Rothman (Jira)" <[email protected]>
| Newsgroups | gmane.comp.jakarta.james.devel |
|---|---|
| Message-ID | <[email protected]> |
Amichai Rothman created JAMES-4139:
--------------------------------------
Summary: Optimize JWT key management
Key: JAMES-4139
URL: https://issues.apache.org/jira/browse/JAMES-4139
Project: James Server
Issue Type: Improvement
Components: webadmin
Affects Versions: 3.8.3
Reporter: Amichai Rothman
The JWT key management is currently inefficient, loading and parsing keys repeatedly. The design and implementation should both be reviewed and optimized where necessary to improve performance. For example:
* OidcJwtTokenVerifier creates a new provider per request instead of creating it once and reusing it for all relevant requests.
* The internal implementations of both JwksPublicKeyProvider and DefaultPublicKeyProvider load or parse keys on every inocation instead of internally caching and reusing the key instances.
* both providers implement get by kid by iterating over all keys instead of using more efficient lookup
--
This message was sent by Atlassian Jira
(v8.20.10#820010)