.RunAs

By default, apps run in the name of the visitor. Visitors are not authorized to write the website of your filesystem. To write it, you have to configure the app to be authorized against the website owner, not the visitor. First, let’s understand the dual access control nature of Boomla.

Dual access control mechanism

In Boomla, every time an app is run, two users are acting, the authorization user and the marker user.

The authorization user is authorized for read/write permission. The marker user is leaving any mark when the filesystem is modified. Think of it as defining the color of the pen that is used to make changes.

To write a collaborative app, it will have to write the filesystem. For that, you will need to change the authorization user to the website owner, because visitor’s don’t have this permission. Generally, you would still want to keep the marker user be the visitor, so that you will know who made the change.

In some cases, you may want to override the marker user as well. Then, the system will record that the website owner made the changes.

Examples

Authorize as the owner, write the filesystem as the visitor:

{
    "link": "",
    "type": "",
    "title": "",
    "statusCode": 0,
    "attr": {
        "authorize string": "owner"
    }
}

Both authorize and write the filesystem as the owner:

{
    "title": "",
    "link": "",
    "type": "accept-1",
    "statusCode": 0,
    "attr": {
        "authorize string": "owner",
        "mark string": "owner"
    }
}