[
https://issues.apache.org/jira/browse/ARTEMIS-2886?focusedWorklogId=478902&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-478902
]
ASF GitHub Bot logged work on ARTEMIS-2886:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Sep/20 02:36
Start Date: 04/Sep/20 02:36
Worklog Time Spent: 10m
Work Description: jbertram edited a comment on pull request #3246:
URL: https://github.com/apache/activemq-artemis/pull/3246#issuecomment-686864244
@luisalves00, I just sent #3254 to deal with this. We just released 2.15.0
so I'm not sure when we'll do the next release. My guess would be in the next
month or so given all the changes that have already been made. In any case, you
can [build your own
release](https://github.com/apache/activemq-artemis/blob/master/docs/hacking-guide/en/building.md)
if necessary.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 478902)
Time Spent: 2h 10m (was: 2h)
> Optimize security auth
> ----------------------
>
> Key: ARTEMIS-2886
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2886
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Fix For: 2.16.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Both authentication and authorization will hit the underlying security
> repository (e.g. files, LDAP, etc.). For example, creating a JMS connection
> and a consumer will result in 2 hits with the *same* authentication request.
> This can cause unwanted (and unnecessary) resource utilization, especially in
> the case of networked configuration like LDAP.
> There is a rudimentary cache for authorization, but it is cleared *totally*
> every 10 seconds by default (controlled via the
> {{security-invalidation-interval setting}}), and it must be populated
> initially which still results in duplicate auth requests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
