Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #23500 Search users as you type no more retrieve cn LDAP attribute
    Infos
    #23500
    Aurélien Tisné (atisne)
    2021-11-09 13:41
    2021-11-09 11:15
    25050
    Details
    Search users as you type no more retrieve cn LDAP attribute

    Using an LDAP, without setting a specific value for the parameter sys_ldap_tooltip_search_attrs, for users not yet added in the Tuleap DB, when I search a user to add as a new member to my team, only the uid of found users are displayed. (Please see attachment.) The common name should also be displayed.

    Authentication & LDAP
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2021-11-09
    Attachments
    By Aurélien Tisné (atisne)
    (26 kB)
    uid_only.png
    User common name is missing
    References
    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2021-11-09 12:13

    You must update, 1/2 of the LDAP configuration is not properly imported, risk is major

    User avatar
    Aurélien Tisné (atisne)2021-11-09 12:03

    Hi. We are using the version 13.1 (Community Edition). (Sorry to miss the artefact 23477 despite my search.)

    Do you know the level of risk to used Tuleap 13.1 without the fix?

    User avatar
    Manuel Vacelet (vaceletm)2021-11-09 11:22

    Which version of Tuleap are you using ? If you are running 13.1-1 you should update on dev ASAP, there is a important fix on LDAP with art #23477

    User avatar
    Aurélien Tisné (atisne)2021-11-09 11:21
    last edited by: Aurélien Tisné (atisne) 2021-11-09 11:21

    In function searchUserAsYouType in plugins/ldap/include/LDAP.class.php, L515, $this->ldapParams['tooltip_search_user'] is set but empty.

    Testing if the value is not empty fix the issue. But I'm not sure it's the best way to fix. May others LDAP parameters have the same issue?