[
https://issues.apache.org/jira/browse/ARTEMIS-2886?focusedWorklogId=477986&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-477986
]
ASF GitHub Bot logged work on ARTEMIS-2886:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 02/Sep/20 17:19
Start Date: 02/Sep/20 17:19
Worklog Time Spent: 10m
Work Description: jbertram commented on pull request #3246:
URL: https://github.com/apache/activemq-artemis/pull/3246#issuecomment-685881000
The `address` parameter was removed as part of the API simplification
because it wasn't required. It wasn't actually being used anywhere. The
`authorize` method gets the `subject` which contains all the roles that the
user has, a `Set` of `Role` objects (which contain the role's name and its
permissions) from the broker's `security-settings`, and the type of check that
needs to be authorized. The name of the address or FQQN isn't really needed.
The security manager just needs to sort through the parameters and see if the
`Subject` has the right roles for the requested check.
Do you have a use-case which requires the address/FQQN? If so, please
elaborate.
----------------------------------------------------------------
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: 477986)
Time Spent: 1h 10m (was: 1h)
> 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: 1h 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)
