How to use Security Templates /default permissions

This article is intended for Filerobot widget customers using v21.07 and higher.

The Security Template /SecTemplate/ only has two permissions configured by default when using the most recent versions of the Filerobot widget. An illustration is shown 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 reason for this is that the "list scope" in the SecTemplate will overwrite the widget's settings in order to prevent a conflict between the settings and the permissions.

This is the intended behaviour because it prevents misconfiguration and widget internal errors.

Our advice is to set up 2 distinct SecTemplates with different list scopes if you want to have a separate root folder.

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