nextcloud-server

Tree: 328b3c47d7

Author	SHA1	Message	Date
Joas Schilling	328b3c47d7	Move stuff from outside lib/ to PSR-4	10 years ago
Robin McCorkell	4717605d22	Fix storage backend class namespaces and move to subdir All classes that were previously \OC\Files\Storage\FooBar are now \OCA\Files_External\Lib\Storage\FooBar	10 years ago
Lukas Reschke	c353d51810	Remove Scrutinizer Auto Fixer	10 years ago
Thomas Müller	682821c71e	Happy new year!	10 years ago
Scrutinizer Auto-Fixer	97f9213da9	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
Morris Jobke	b945d71384	update licence headers via script	10 years ago
Robin McCorkell	38a260e963	Revert "Implement more fine-grained external storage permissions model" This reverts commit `0b97a05e7b`. This reverts commit `d2e3c17c00`. This reverts commit `cc88c5f4b8`.	10 years ago
Robin McCorkell	f0c8cfa9a6	Validate permissions for created admin storages, auth mechanism Backend and auth mechanism permissions are checked on storage creation, both for personal storages and for admin storages	10 years ago
Robin McCorkell	cc88c5f4b8	Implement more fine-grained external storage permissions model VisibilityTrait -> PermissionsTrait PermissionsTrait stores two sets of data, $permissions and $allowedPermissions (analogous to $visibility and $allowedVisibility of VisibilityTrait). Each set is a map of user type ('admin' or 'personal') to permissions (mounting permission, create permission). The result is that a backend can now be restricted for creation, while still allowing it to be mounted. This is useful for deprecating backends or auth mechanisms, preventing new storages being created, while still allowing existing storages to be mounted.	10 years ago
Robin McCorkell	c572631087	Unit tests for new backend API	10 years ago
Robin McCorkell	1eeca031f8	Split backend identifiers from the class name Prior to this, the storage class name was stored in mount.json under the "class" parameter, and the auth mechanism class name under the "authMechanism" parameter. This decouples the class name from the identifier used to retrieve the backend or auth mechanism. Now, backends/auth mechanisms have a unique identifier, which is saved in the "backend" or "authMechanism" parameter in mount.json respectively. An identifier is considered unique for the object it references, but the underlying class may change (e.g. files_external gets pulled into core and namespaces are modified).	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	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
Vincent Petry	34c8b1ac77	Mount options for ext storage are now passed around The mount options are now passed to the UI and stored in a hidden field. The ext storage controllers and services also know how to load/save them from the legacy config.	11 years ago
Vincent Petry	ce94a998dd	Use storage id + appframework for ext storage CRUD - Added StorageConfig class to replace ugly arrays - Implemented StorageService and StorageController for Global and User storages - Async status checking for storages (from Xenopathic) - Auto-generate id for external storage configs (not the same as storage_id) - Refactor JS classes for external storage settings, this mostly moves/encapsulated existing global event handlers into the MountConfigListView class. - Added some JS unit tests for the external storage UI	11 years ago

1 Commits (328b3c47d7fdf61b6de3c2d9129d392d3a9f5a87)