[jira] [Commented] (ARTEMIS-4263) support access to our JaasCallbackhandler from a jdk http Authenticator

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719756#comment-17719756 ] 

ASF subversion and git services commented on ARTEMIS-4263:
----------------------------------------------------------

Commit cf3afc409683b8d279fe7bb3cd4c32ce6b8fdb98 in activemq-artemis's branch refs/heads/main from Gary Tully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=cf3afc4096 ]

ARTEMIS-4263 authenticator to delegate to artemis jaas login modules and populate callback handler


> support access to our JaasCallbackhandler from a jdk http Authenticator
> -----------------------------------------------------------------------
>
>                 Key: ARTEMIS-4263
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4263
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: JAAS
>    Affects Versions: 2.28.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> To allow the jolokia jvm agent to utilise jaas with our callback handler, it is necessary to provide a wrapper that is aware of the capabilities of the various artemis login modules and provide the necessary callback implementation
> httpserver supports an extension point in the form of a {{com.sun.net.httpserver.Authenticator}} that we can use.  the jolokia jvm agent has an authenticator that does jaas but is limited to plain credentials. We can plug in a similar Artemis jaas delegating authenticator and do proper rbac when the jolokia jvm agent is in play.
> This will allow us to reduce the surface are that we expose to support jolokia, avoiding the need for jetty. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)