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 #11621 LDAP display name vs group name in sync view
    Actions
    Infos
    #11621
    Jonathan Palm (palm)
    2018-08-09 10:31
    2018-06-14 08:21
    11963
    Details
    LDAP display name vs group name in sync view
    In the admin view where we bind an LDAP group to sync group membership, the display name is shown, but an error is present saying it cannot find this as one should instead use the underlying LDAP name.

    The UI should be altered so that one can find the LDAP group through either the underlying LDAP name or the display name, or at least so it stays consistent.
    Authentication & LDAP
    10.1
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Patricia Carrasco (pcar), Stephan Bill (stephanbill), Kristofer Sandlund (krisan)
    Stage
    Empty
    Closed
    2018-08-09
    Attachments
    Artifact links

    Requests

    Releases

    is Covered by

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    request #10146 Tuleap Requests LDAP Groups and Common Name Closed 2018-09-08 10:37 Patrick Pogscheba (patrock)

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #11518 Tuleap Releases 10.4 Delivered 2018-20-08 13:51 Manuel Vacelet (vaceletm)
    By Jonathan Palm (palm)
    (7 kB)
    mockup_alt1.png
    One version
    By Jonathan Palm (palm)
    (7 kB)
    mockup_alt2.png
    Another mockup
    References
    Referencing request #11621

    Artifact Tracker v5

    request #10146 LDAP Groups and Common Name

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/86/11886/8' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 155cd706b3
    User avatar Yannis ROSSETTO (rossettoy) , 2018-08-08 16:29
    (request #11621) LDAP group search using display name 40721e5e58
    User avatar Jonathan Palm (palm) , 2018-08-08 14:41
    Adapt information for static ugroup modal 99b0f121b9
    User avatar Yannis ROSSETTO (rossettoy) , 2018-08-08 16:43
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2018-08-09 10:31
    gerrit #12252 has been integrated in Tuleap 10.3.99.123.


    Thanks for the contribution @palm!
    • Status changed from Under implementation to Closed
    • Close date set to 2018-08-09
    User avatar
    Manuel Vacelet (vaceletm)2018-07-17 17:19

    We are busy finishing 10.3 release, we will review you other contribution after the release.

    User avatar
    Jonathan Palm (palm)2018-07-16 15:05
    I've made some changes according to the feedback. Feel free to check them out on gerrit when you've got the time :)
    User avatar
    Jonathan Palm (palm)2018-06-28 08:18
    Alright, "alt2" it is. I'll go ahead and start implementing this ASAP. I appreciate the feedback!
    User avatar
    Manuel Vacelet (vaceletm)2018-06-27 15:37

    Could you share a pseudo mockup of what you have in mind in term of UI (even a wireframe would be OK) ?

    User avatar
    Jonathan Palm (palm)2018-06-27 11:25
    It is precisely the behavior of $sys_ldap_search_user that I want to replicate for groups.

    I think having a small UI tweak could be useful, so that it is possible to see both the LDAP name and the display name when searching. This becomes especially useful when the LDAP cn attribute is completely non-descriptive and unrelated to the group name one would want to show to the project admin. Simply keeping it on the form of "display_name (cn)" in autocomplete would probably suffice for us.

    Would this UI tweak be reasonable?
    User avatar
    Manuel Vacelet (vaceletm)2018-06-27 10:35

    I'm not sure the UI should be aware of the CN vs display_name, I think it would be better to extends the search to add an extra field (maybe as it's done for $sys_ldap_search_user).

    That would mean a new variable $sys_ldap_search_group, if the variable is defined, it's used to search, otherwise there is fallback on cn search.

    What do you think ?

    User avatar
    Jonathan Palm (palm)2018-06-27 08:27
    So the feature would be to make it so that the LDAP plugin will either search for the cn (the current behavior) or a "display name" (should be defined in the config) and make suggestions depending on the best match