Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scoped links #6844

Closed
exalate-issue-sync bot opened this issue Apr 29, 2022 · 1 comment · Fixed by #7769
Closed

Scoped links #6844

exalate-issue-sync bot opened this issue Apr 29, 2022 · 1 comment · Fixed by #7769
Labels
Type:Story User Story

Comments

@exalate-issue-sync
Copy link

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
@exalate-issue-sync
Copy link
Author

Exalate commented: This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type:Story User Story
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant