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 #8756 Revoked token should no longer be usable
    Actions
    Infos
    #8756
    Manuel Vacelet (vaceletm)
    2017-02-03 17:12
    2016-01-06 16:05
    8873
    Details
    Revoked token should no longer be usable
    As of today a revoked token is valid until something affect apache config and the server is restarted.

    Cache invalidation is only possible with server restart as of today so to avoid to let in user'ss hands an acceptable tradeof would be to force server restart during system check if one token was invalidated.

    Technical information:
    * cache lifetime and number of users cached by repo will be configurable by a siteadmin. When a parameter is modified, codendi_svnroot.conf must be regenerated.
    * default cache lifetime is 5mn and default number of users cached is 10
    * granularity of cache lifetime parameter is minute
    * if cache lifetime is set to 0 mn, a user in cache is not authenticated again until the cache is cleared
    * cache lifetime is set by user and not for the entire cache. The cache will not be cleared completely at the end of the lifetime, only user older than this lifetime will be invalidated and authenticated again.
    * same values are used by the plugin
    SCM/Subversion
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2017-02-03
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #9535 Tuleap Releases 9.1 Delivered 2016-11-14 11:24 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #8756

    Git commit

    tuleap/tuleap/stable

    SVN authentication cache can be configured 81844ca48b
    User avatar Thomas Gerbet (tgerbet) , 2016-11-04 16:41
    SVN authentication cache has an expiration delay b59356e738
    User avatar Thomas Gerbet (tgerbet) , 2016-11-07 10:42
    Be able to see the SVN authentication cache parameters in the site administration e730bd9cbc
    User avatar Thomas Gerbet (tgerbet) , 2016-11-08 14:22
    Be able to modify the SVN authentication cache parameters in the site administration b73b88c9e9
    User avatar Thomas Gerbet (tgerbet) , 2016-11-08 16:53
    Referenced by request #8756

    Artifact Tracker v5

    rel #9535 9.1

    Other

    gerrit #6868
    gerrit #6909
    gerrit #6915
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2016-02-02 14:14

    I have added some information in the original submission to know how this request should be fixed.

    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Manuel Vacelet (vaceletm)2016-01-21 16:27
    Sounds good, however, the cache TTL should be configurable (5mn might be too low on heavily loaded servers)
    User avatar
    Thomas Gerbet (tgerbet)2016-01-21 16:09
    I'm afraid the proposed way could be costly especially you have a lot of users playing with SVN tokens.
    May I propose an intermediate solution: do you think is it acceptable to invalidate the whole cache every five minutes for example? This means when a SVN token is revoked in the worst case scenario his remaining lifetime is 5mn.
    • Status changed from New to Acknowledged