[jira] [Work logged] (ARTEMIS-3542) Avoid requesting the root attribute when binding a user to LDAP

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-3542?focusedWorklogId=670679&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-670679 ]

ASF GitHub Bot logged work on ARTEMIS-3542:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Oct/21 12:15
            Start Date: 27/Oct/21 12:15
    Worklog Time Spent: 10m 
      Work Description: MM53 opened a new pull request #3820:
URL: https://github.com/apache/activemq-artemis/pull/3820


   Check getAttributes with dn of user entry to avoid missing permissions


-- 
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.

To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 670679)
    Remaining Estimate: 0h
            Time Spent: 10m

> Avoid requesting the root attribute when binding a user to LDAP
> ---------------------------------------------------------------
>
>                 Key: ARTEMIS-3542
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3542
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: JAAS
>            Reporter: Marlon Müller
>            Priority: Minor
>             Fix For: 2.20.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently the bindUser-method of the LDAPLoginModule tries to verify the user through requesting the root attribute of the LDAP tree. This check fails if the user is not allowed to access the root element although everything else is working properly. 
> To fix this problem the user should only request its own LDAP attribute as this will always be possible.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)