How to use Security Templates /default permissions

This article is dedicated to Filerobot widget users version compatible with v21.07 and higher.

By default, when using the latest version of the Filerobot widget, there are only two permissions set on the Security Template /SecTemplate/, see the example below: 

 

Template:

{
"permissions": [

"OBJECTS_LIST",
"FILE_UPLOAD"
],
"description": "dev (from FileRobot UI)",
"list_scope": [
"/dev/*"
],
"upload_scope": [
"/dev/*"
]
}

 

You may encounter the following error in a scenario where you want to have a separate root folder:

Error: “explorerService.getPublicConstants is not a function” where the rootFolderPath option on the Explorer will not work for your container.

 

The explanation for this is that the “list_scope” in the SecTemplate will overwrite the settings of the widget in order to avoid conflict between the settings and the permissions.

 

This is in fact the intended behaviour as it prevents misconfiguration and widget internal error.

If you want to have a separate root folder, our recommendation would be to set 2 different SecTemplates with different list scopes.

 

For your reference, you could explore the solution in depth using the resources below:

API Access Keys and Security Templates Listing limits  Requesting an Access Key 

 

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.