[ https://issues.apache.org/jira/browse/ARTEMIS-4263?focusedWorklogId=859674&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-859674 ]
ASF GitHub Bot logged work on ARTEMIS-4263: ------------------------------------------- Author: ASF GitHub Bot Created on: 28/Apr/23 14:11 Start Date: 28/Apr/23 14:11 Worklog Time Spent: 10m Work Description: gtully commented on code in PR #4458: URL: https://github.com/apache/activemq-artemis/pull/4458#discussion_r1180465177 ########## artemis-server/src/main/java/org/apache/activemq/artemis/spi/core/security/jaas/AuthenticatorAdapter.java: ########## @@ -0,0 +1,128 @@ +/** Review Comment: think javadoc is ok for the description, why not? Issue Time Tracking ------------------- Worklog Id: (was: 859674) Time Spent: 1h 20m (was: 1h 10m) > 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: 1h 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)