[
https://issues.apache.org/jira/browse/ARTEMIS-4263?focusedWorklogId=859577&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-859577
]
ASF GitHub Bot logged work on ARTEMIS-4263:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Apr/23 08:12
Start Date: 28/Apr/23 08:12
Worklog Time Spent: 10m
Work Description: gtully commented on PR #4458:
URL:
https://github.com/apache/activemq-artemis/pull/4458#issuecomment-1527166106
thanks Justin, fixed the commit message.
the use case is the jolokia jvm agent that uses the jdk http stack, it can
do jaas delegation via a user/pass authenticator but it does not know about the
artemis callback handler so cannot populate all of our login modules. This is
an authenticator that knows about artemis. It is generic, the autnenticator is
an extension point for the jdk http stack, nothing jolokia specific in this.
Issue Time Tracking
-------------------
Worklog Id: (was: 859577)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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
> Jolokia supports an externsion point in the form of a
> com.sun.net.httpserver.Authenticator that we can use.
> 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)
