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 #12406 User autocomplete mix users when a ldap id is the same than a tuleap user id
    Actions
    Infos
    #12406
    Marie Ange Garnier (marieange)
    2018-10-31 13:47
    2018-10-17 16:34
    13075
    Details
    User autocomplete mix users when a ldap id is the same than a tuleap user id

    How to reproduce:

    •  Create a Tuleap LDAP user test.
    • Renaming him to test2
    • Create a new user with tuleap login test

    You should have somthing like the table below for your users:

    | tuleap login | LDAP login |
    | test2            | test            |
    | test              | mytestuser |

     

    Authentication & LDAP
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Marie Ange Garnier (marieange)
    Declined
    Empty
    Attachments
    Empty
    References
    Referencing request #12406

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/35/12935/7' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD dc2f0f43f1
    User avatar Joris MASSON (jmasson) , 2018-10-26 12:01
    request #12406 User autocomplete mix users when a ldap id is the same than a tuleap user id 4a654260a4
    User avatar Marie Ange Garnier (marieange) , 2018-10-26 10:43
    Merge commit 'refs/changes/20/13020/1' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD aa7fa078f4
    User avatar Marie Ange Garnier (marieange) , 2018-10-31 13:46
    Revert "request #12406 User autocomplete mix users when a ldap id is the same than a tuleap user id" 928ac65c90
    User avatar Yannis ROSSETTO (rossettoy) , 2018-10-31 13:04
    Referenced by request #12406

    Artifact Tracker v5

    rel #12268 10.7

    Other

    gerrit #12935
    gerrit #13020
    Display settings

    Follow-ups

    User avatar
    Marie Ange Garnier (marieange)2018-10-31 13:28
    Finally we do not want to support this use case,
    when a ldap username is bound to a different tuleap username,
    then it's the responsibility of administrator to manage it (by renaming user or updating ldap user login)
    • Status changed from Reopen to Declined