Scoped links #6844
Description
Description
User Stories
As a user I want to get a link to a resource as easily and quickly as possible. I don't want to decide whether I need a 'private' or a 'public' link in the first place. Still, I might want to decide (e.g., for security reasons) for whom the link is usable (link scope): for everybody (public) / only invited people (private).
Value
- Highly increased usability
- Part of new sharing concept
- data loss prevention
Acceptance Criteria
- Users can create links for files and folders just like with public links today
- There is an option for the user to decide about the scope of the link
- a) everybody can use it without authentication ("everyone with the link")
- b) only authenticated users who have access to the resource can use it ("only invited people")
- Changing the link scope does not have an impact on the link URL
- The link URLs comply with the definition in ADR 11
- When an unauthenticated user uses a link with scope 'only invited people', they will be asked to authenticate
- When an authenticated user uses a link with scope 'only invited people' but they don't have access to the resource, they see an error message (same for deleting/moving the resource)
- When an unauthenticated user uses a link with scope "everyone with the link", they see the regular public link view (and have the ability to authenticate)
Definition of done
- Functional requirements
[ ] functionality described in the user story works
[ ] acceptance criteria are fulfilled - Quality
[ ] codre review happened
[ ] CI is green
[ ] critical code received unit tests by the developer
[ ] automated tests passed (if automated tests are not available, this test needs to be created and passed - Non-functional requirements
[ ] no sonar cloud issues