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 #12535 User avatar and profile are not accessible when the LDAP UID is not identical to the Tuleap username
    Actions
    Infos
    #12535
    Thomas Gerbet (tgerbet)
    2018-11-20 14:31
    2018-11-20 13:20
    13245
    Details
    User avatar and profile are not accessible when the LDAP UID is not identical to the Tuleap username
    The avatar and profile URLs are generated from the Tuleap username but when displaying the pages Tuleap tries to get the user from its login name. This might fails and results in a 404 if the login name is not identical to the Tuleap username.
    Other
    10.7
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2018-11-20
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #12269 Tuleap Releases 10.8 Delivered 2018-12-07 15:14 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #12535

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/60/13160/1' of ssh://gerrit.tuleap.net:29418/tuleap fb2fc2589f
    User avatar Manuel Vacelet (vaceletm) , 2018-11-20 14:39
    request #12535: User avatar and profile are not accessible when the LDAP UID is not identical to the Tuleap username e80abbebf9
    User avatar Thomas Gerbet (tgerbet) , 2018-11-20 13:22
    Referenced by request #12535

    Artifact Tracker v5

    rel #12269 10.8

    Other

    gerrit #13160
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2018-11-20 13:26
    A patch is under review: gerrit #13160.
    • Summary
      -User avatar and profile is not accessible when the LDAP UID is different than the the Tuleap username 
      +User avatar and profile are not accessible when the LDAP UID is not identical to the Tuleap username 
    • Status changed from Under implementation to Under review