•  
      story #9409 define FRS permissions for packages and releases
    Summary
    project admin
    define FRS permissions for packages and releases
    I can better control who access my releases and have a consistent interface to manage the people who can write

    At FRS package creation/update, the selector to set specific read permissions is updated to take into account minimal permissions defined at FRS admin level (ie. if READ is granted to "project_members", it won't be possible to grant READ to all_users for a given package)
    To make it consistent, FRS release creation/update should also have the same behaviour (not possible to select a Release level a granted access that is not consistent with what is defined at Package, Service, Project & Site level).
    The FRS service will only be visible by people who have at least READ access to it (like mediawiki, ...)

    Special notes

    A special attention should be taken to not break all the elements that rely on FRS
    Soap & CLI
    REST
    Webdav
    Empty
    Empty
    Status
    Empty
    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
    #9409
    Marie Ange Garnier (marieange)
    2016-09-05 09:34
    2016-08-19 08:56
    4597

    References

    Follow-ups