Content
Updated by Jan Sandbrink 3 days ago
**As** ### Steps to reproduce
1. Have a user,
**I want to** have Nextcloud storage permissions updated synchronously that authenticates through SSO
2. Login as a **new** SSO user to OpenProject and Nextcloud, so that your account is provisioned on both sides
1. The SSO user must not be admin in more cases,
**so that** I immediately see my Nextcloud, because it must not be allowed to read files in NC before OpenProject sets up access permissions
3. Go to a project where you should be allowed to see linked files
4. Access a work package's files tab with already linked files
### What is the buggy behavior?
The linked file shows slightly greyed out, with a hover text indicating that you do not have access to the file.
Clicking on the file works as expected and after receiving storage access. a page refresh, the file shows as readable.
####
#### Acceptance criteria ### What is the expected behavior?
* Users can see files Even first-time users should immediately know that they have access to immediately...
* after performing files linked to a work package.
**Out of scope:** We decided that we will not try to fix the OAuth flow for case where the first-time user immediately clicks on a storage
* after files tab link. In general if users are "too quick" seeing the files tab, they might still see the errorneous behaviour. But a user logging in and authenticating then navigating to a storage via SSO
work package where they should be allowed to see files, should be able to see their access from the beginning.
### Environment information
**OpenProject installation type**
* Synchronous remote calls to update the user's permissions are performed in a way that the duration does not scale with the number of users or projects Hosted cloud edition
**OpenProject version**
QA Edge
**Browser**
* [ ] Chrome
* [x] Firefox
* [ ] Safari
* [ ] Mobile Safari
* [ ] Other (please specify)
1. Have
**I want to** have
2. Login as a **new** SSO user to OpenProject and Nextcloud, so that your account is provisioned on both sides
1. The SSO user must not be admin
**so that** I immediately see my
3. Go
4. Access a work package's files tab with already linked files
### What is the buggy behavior?
The linked file shows slightly greyed out, with a hover text indicating that you do not have access to the file.
Clicking on the file works as expected and
####
#### Acceptance criteria
* Users can see files
* after performing
**Out of scope:** We decided that we will not try to fix
* after
### Environment information
**OpenProject installation type**
**OpenProject version**
QA Edge
**Browser**
* [ ] Chrome
* [x] Firefox
* [ ] Safari
* [ ] Mobile Safari
* [ ] Other (please specify)