Content
View differences
Updated by Jan Sandbrink about 1 year ago
### Steps to reproduce
1. Have a Nextcloud storage 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 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 a page refresh, the file shows as readable.
### What is the expected behavior?
Even first-time users should immediately know that they have access to files linked to a work package.
**Out of scope:** We decided that we will not try ### Environment information
_Please check and fill out the following details to fix the case where the first-time user immediately clicks on a 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 help us identify in what versions and then navigating to a work package where they should be allowed to see files, should be able to see their access from distributions of OpenProject the beginning.
### Environment information error occurs_
**OpenProject installation type**
* Hosted cloud edition
**OpenProject version**
QA Edge
**Browser**
* [ ] Chrome
* [x] Firefox
* [ ] Safari
* [ ] Mobile Safari
* [ ] Other (please specify)
1. Have a Nextcloud storage 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 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 a page refresh, the file shows as readable.
### What is the expected behavior?
Even first-time users should immediately know that they have access to files linked to a work package.
**Out of scope:** We decided that we will not try
_Please check and fill out the following details
### Environment information
**OpenProject installation type**
* Hosted cloud edition
**OpenProject version**
QA Edge
**Browser**
* [ ] Chrome
* [x] Firefox
* [ ] Safari
* [ ] Mobile Safari
* [ ] Other (please specify)