nextcloud-server

Tree: 4255dd2b39

Author	SHA1	Message	Date
Vincent Petry	4255dd2b39	Properly set exception in FailedStorage	10 years ago
Robin Appelman	6990100e6e	allow availability recheck for external storages	10 years ago
Robin Appelman	e420ae068c	handle exception in availibilty check	10 years ago
Robin Appelman	2e3a5ccaaa	show failed external storages properly	10 years ago
Robin McCorkell	3fe802d931	Introduce 'login credentials' auth mechanism Stores user credentials in the database after user login, uses the new CredentialsManager class	10 years ago
Thomas Müller	682821c71e	Happy new year!	10 years ago
Robin Appelman	f27e98a3e2	Migrate files external for the user that the filesystem is being setup for	10 years ago
Robin Appelman	a1898dc2bf	db config backend for files_external	10 years ago
Scrutinizer Auto-Fixer	dcbd603514	Scrutinizer Auto-Fixes This commit consists of patches automatically generated for this project on https://scrutinizer-ci.com	10 years ago
Morris Jobke	8366ce2767	deduplicate @xenopathic	10 years ago
Robin McCorkell	2404333300	Perform visibility checks on storages StoragesService::getStorages() will check the visibility of the backend and auth mechanism for the storage, and if either are not visible to the user (aka disabled by admin) then the storage will be filtered out. The original method StoragesService::getAllStorages() still exists in case such storages need to be detected, but its use is discouraged.	10 years ago
Robin McCorkell	ca7b4a42f9	Fix external storage priority logic	10 years ago
Robin Appelman	d14252d9c7	make sure we actually have an object store	10 years ago
Robin McCorkell	b6eb952ac6	Propagate auth mechanism/backend failures to filesystem layer Failure to prepare the storage during backend or auth mechanism manipulation will throw an InsufficientDataForMeaningfulAnswerException, which is propagated to StorageNotAvailableException in the filesystem layer via the FailedStorage helper class. When a storage is unavailable not due to failure, but due to insufficient data being available, a special 'indeterminate' status is returned to the configuration UI.	10 years ago
Robin McCorkell	272a46ebe1	Authentication mechanisms for external storage backends A backend can now specify generic authentication schemes that it supports, instead of specifying the parameters for its authentication method directly. This allows multiple authentication mechanisms to be implemented for a single scheme, providing altered functionality. This commit introduces the backend framework for this feature, and so at this point the UI will be broken as the frontend does not specify the required information. Terminology: - authentication scheme Parameter interface for the authentication method. A backend supporting the 'password' scheme accepts two parameters, 'user' and 'password'. - authentication mechanism Specific mechanism implementing a scheme. Basic mechanisms may forward configuration options directly to the backend, more advanced ones may lookup parameters or retrieve them from the session New dropdown selector for external storage configurations to select the authentication mechanism to be used. Authentication mechanisms can have visibilities, just like backends. The API was extended too to make it easier to add/remove visibilities. In addition, the concept of 'allowed visibility' has been introduced, so a backend/auth mechanism can force a maximum visibility level (e.g. Local storage type) that cannot be overridden by configuration in the web UI. An authentication mechanism is a fully instantiated implementation. This allows an implementation to have dependencies injected into it, e.g. an \OCP\IDB for database operations. When a StorageConfig is being prepared for mounting, the authentication mechanism implementation has manipulateStorage() called, which inserts the relevant authentication method options into the storage ready for mounting.	10 years ago
Robin McCorkell	a6a69ef1df	Introduce UserGlobalStoragesService UserGlobalStoragesService reads the global storage configuration, cherry-picking storages applicable to a user. Writing storages through this service is forbidden, on punishment of throwing an exception. Storage IDs may also be config hashes when retrieved from this service, as it is unable to update the storages with real IDs. As UserGlobalStoragesService and UserStoragesService share a bit of code relating to users, that has been split into UserTrait. UserTrait also allows for the user set to be overridden, rather than using the user from IUserSession. Config\ConfigAdapter has been reworked to use UserStoragesService and UserGlobalStoragesService instead of OC_Mount_Config::getAbsoluteMountPoints(), further reducing dependance on that horrible static class.	10 years ago
Robin McCorkell	37beb58c6f	Introduce BackendService for managing external storage backends Backends are registered to the BackendService through new data structures: Backends are concrete classes, deriving from \OCA\Files_External\Lib\Backend\Backend. During construction, the various configuration parameters of the Backend can be set, in a design similar to Symfony Console. DefinitionParameter stores a parameter configuration for an external storage: name of parameter, human-readable name, type of parameter (text, password, hidden, checkbox), flags (optional or not). Storages in the StoragesController now get their parameters validated server-side (fixes a TODO).	10 years ago
Jenkins for ownCloud	b585d87d9d	Update license headers	11 years ago
Morris Jobke	06aef4e8b1	Revert "Updating license headers" This reverts commit `6a1a4880f0`.	11 years ago
Jenkins for ownCloud	6a1a4880f0	Updating license headers	11 years ago
Robin Appelman	95a145f67f	Load mount specific options from the mount config	11 years ago
Robin Appelman	a369d78124	Use the mount config api for files_external	11 years ago

22 Commits (4255dd2b396050e757f77db86063f0f1420a87d5)