/pps/system/authorization/control

Change user's remembered decisions for grant/denial of application capabilities

Publishers: Any app
Subscribers: coreServices; any app

Note: This type of object is known as a server object, a special PPS object designed for point-to-point communication between a server and one or more clients. For details, see "Server objects" in the QNX Persistent Publish/Subscribe Developer's Guide.

Message/response format

Commands sent to the /pps/services/authorization/control object are of the form:

msg::command_string\nid::ID_number\ndat:json:{JSON_data}

Responses always reflect the command_string and ID_number that were sent in the message, along with any errors:

res::command_string\nid::ID_number\ndat:json:{JSON_data}\nerr::errno_number\nerrstr::error_description

The set_permission command

This object accepts only one command:

msg::	id::	dat:json:
set_permission	Number	`{"parameter":"value", "parameter":"value", ...}`

Parameters and values are as follows:

Parameter	Value
`application`	String giving the qualified (with EcoID) name of the application from BAR manifest.
`capability`	String giving the capability ID. Possible values: `access_shared` `record_audio` `read_geolocation` `use_camera` `read_device_identifying_information`
`rule`	The permission to set: allow deny prompt

Response

res::	id::	dat:json:	err::	errstr::
set	Number (whatever was sent in `id::`)	`result` (`ok` or `failed`)	`errno_number`	as appropriate