Content
View differences
Updated by Jan Sandbrink about 1 year ago
### Steps to reproduce
1. Have a storage authenticating via SSO only
1. authentication must fail for the user, e.g. by misconfiguring storage or by user account not existing in remote storage yet
2. the storage must not be configured for two-way oauth in the background
2. Add the storage to a project and navigate to the project
3. Click on the storage link in the left-hand-side menu
### What is the buggy behavior?
An HTTP 500 error is indicated, with an unspecific error message.
### What is the expected behavior?
The error message should indicate an authentication problem. Optionally allow opening the storage should be opened at a generic location.
Side note: For users not yet existing in remote storage, this may even fix the authentication problems.
1. Have a storage authenticating via SSO only
1. authentication must fail for the user, e.g. by misconfiguring storage or by user account not existing in remote storage yet
2. the storage must not be configured for two-way oauth in the background
2. Add the storage to a project and navigate to the project
3. Click on the storage link in the left-hand-side menu
### What is the buggy behavior?
An HTTP 500 error is indicated, with an unspecific error message.
### What is the expected behavior?
The
Side note: For users not yet existing in remote storage, this may even fix the authentication problems.