Lookup Onedata user to credentials mapping
Returns mapping of the Onedata user to user on the specific storage stored in LUMA DB.
Path parameters
| Parameter | Type & Description |
|---|---|
| id required | string The Id of a storage for which user mapping should be returned. |
| onedata_user_id required | string The Id of a user for which mapping should be returned. |
Request Examples
onepanel-rest-cli -u onepanel:$PASSPHRASE lumaGetOnedataUserToCredentialsMapping id=$STORAGE_ID onedata_user_id=$ONEDATA_USER_ID --host https://$OP_PANEL_HOST:9443
Responses
Result of mapping the Onedata user to storage user.
storageCredentials 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.
Unauthorized request.
Forbidden request.
Storage or user mapping does not exist.
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.