You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/04/06 19:56:00 UTC
[jira] [Updated] (ARTEMIS-5901) Support UPN for client certificate authentication
[ https://issues.apache.org/jira/browse/ARTEMIS-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated ARTEMIS-5901:
------------------------------------
Labels: pull-request-available (was: )
> Support UPN for client certificate authentication
> -------------------------------------------------
>
> Key: ARTEMIS-5901
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5901
> Project: Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently the key used for the authentication cache uses a hash based on the username, password, and DN of the TLS cert (if available). This typically results in a unique value for each user. However, if a custom JAAS {{LoginModule}} is used that doesn't use these credentials (e.g. it uses certificate's *UPN* instead of DN) then the authentication cache key will not necessarily be unique for each user.
> Currently the only option in this situation is to disable authentication caching, but that can adversely impact performance.
> Therefore, the broker should support some way to customize the authentication cache key (e.g. via a plugin).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org