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.

    •  
      story #30336 use a personal access key to do SVN operations
    Actions
    Summary
    user
    use a personal access key to do SVN operations
    • I can use the same personal access key to access the REST API and SVN repositories
    • I have a consistent experience when I need a personal token to access a SVN repository
    • Personal access key have a new SVN scope to access SVN repositories
    • It is not possible to create new SVN tokens, a personal access key must be used instead
    • The whole "SVN tokens" panel is not shown when the user does not have existing SVN tokens
    Empty
    Empty
    Status
    SCM/Subversion
    Done
    Development
    • [ ] Does it involves User Interface? 
    • [ ] Are there any mockups?
    • [ ] Are permissions checked?
    • [ ] Does it need Javascript development?
    • [ ] Does it need a forge upgrade bucket?
    • [ ] Does it need to execute things in system events?
    • [ ] Does it impact project creation (templates)?
    • [ ] Is it exploratory?
    Empty
    Details
    #30336
    Thomas Gerbet (tgerbet)
    2023-01-10 11:02
    2023-01-04 16:18
    3665

    References
    Artifact links
    Empty
    Referencing story #30336

    Artifact Tracker v5

    rel #30335 14.5

    Git commit

    tuleap/tuleap/stable

    Users can use an access key to do SVN operations fb3d3eacba
    User avatar Thomas Gerbet (tgerbet) , 2023-01-05 15:11
    Remove the possibility to create new SVN tokens 2f4b30f6b9
    User avatar Thomas Gerbet (tgerbet) , 2023-01-06 17:42
    Referenced by story #30336

    Other

    gerrit #27575
    gerrit #27585
    Display settings

    Follow-ups