Insert Onedata user to credentials mapping into local feed
Adds mapping of Onedata user to user on the specific storage to local feed. Returns an error if the storage has a different LUMA feed than local.
Path parameters
| Parameter | Type & Description |
|---|---|
| id required | string The Id of a storage for which user mapping should be added. |
Request body
New user mapping
onedataUser object (LumaOnedataUser) Representation of Onedata user.
Representation of Onedata user.
Name of scheme used to represent user identity.
Name of scheme used to represent user identity.
storageUser object (LumaStorageUser) Credentials identifying user on the local storage resources.
Credentials identifying user on the local storage resources.
storageCredentials required object (LumaStorageCredentials) Credentials that will be used to perform actions on the local storage resources in the context of the Onedata user.
Credentials that will be used to perform actions on the local storage resources in the context of the Onedata user.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
This value will be used in the Oneclient to display it's owner UID if the corresponding user is owner of the file.
Request Examples
cat user_mapping.json | onepanel-rest-cli -u onepanel:$PASSPHRASE localFeedAddOnedataUserToCredentialsMapping id=$STORAGE_ID --host https://$OP_PANEL_HOST:9443 -
Responses
Onedata user mapping for given storage has been successfully added.
Unauthorized request.
Forbidden request.
Storage or user does not exist or LUMA feed is not local.
Internal server error.
error object (ErrorDetails) Object describing an error.
Object describing an error.
String identifying the error type. Does not change between error instances.
Human readable error description. May contain information specific to given error instance.
Details about the error instance. The object schema is specific to each error type.
Example
{
"error": {
"id": "badValueString",
"details": {
"key": "name"
},
"description": "Bad value: provided \"name\" must be a string."
}
}Services needed to fulfill this request are not running.