Content
View differences
Updated by Dominic Bräunlein about 2 years ago
**As** a administrator responsible for file storages
**I want to** have my OneDrive/SharePoint storage settings validated against the storage provider before the settings are saved
**so that** I get immediate feedback whether the entered values can be correct.
**Acceptance criteria**
* When saving the OAuth section, a request to the backend will be send and used to validate the setup. setup.
* Validation errors can be:
* Drive ID invalid
* Client ID or Tenant invalid
* Client secret invalid
* API Permission in Azure application missing
* While the validation request is send there should be a spinner on the submit button
* When a unexpected error happens e.g. a network error we should show a toast with the error and not allow the user to enter the next section
* Besides the initial validation there is a second validation in the end of the setup.
* When automatically managed project folders was activated the modal another validation request is done to check the content.
* When files are in the drive, a error message shows up and the user can not save the storage
* The user has to change the drive ID or remove the files first first
* Then the user can save the storage again and the validation will start another time
**I want to** have my OneDrive/SharePoint storage settings validated against the storage provider before the settings are saved
**so that** I get immediate feedback whether the entered values can be correct.
**Acceptance criteria**
* When saving the OAuth section, a request to the backend will be send and used to validate the setup.
* Validation errors can be:
* Drive ID invalid
* Client ID or Tenant invalid
* Client secret invalid
* API Permission in Azure application missing
* While the validation request is send there should be a spinner on the submit button
* When a unexpected error happens e.g. a network error we should show a toast with the error and not allow the user to enter the next section
* Besides the initial validation there is a second validation in the end of the setup.
* When automatically managed project folders was activated the modal another validation request is done to check the content.
* When files are in the drive, a error message shows up and the user can not save the storage
* The user has to change the drive ID or remove the files first
* Then the user can save the storage again and the validation will start another time