Monitor Permission Explanation
registrar Application permitted to add/remove other applications from the OCAP database.
service Application permitted to modify its service contexts.
servicemanager Application permitted to create its own service context.
security Application can determine the permissions of other applications.
reboot Application can reboot the box.
systemevent Causes monitor application to be affected by actions such as a reboot.
handler.appFilter Application can control if the OCAP middleware will load broadcast applications.
handler.resource Permits an application to resolve resource conflicts.
handler.closedCaptioning Application can display closed captions.
filterUserEvents Application can filter incoming user events.
handler.podResource Application can access the CableCARD.
handler.eas Application can process Emergency Alert Messages.
setCCIBits Application can change the copy control processing of the CableCARD.
setDownRes Application can constrain video output on the VideoOutputPort.
setVideoPort Application can manipulate digital video output ports such as DVI and HDMI and analog interfaces such as component video output.
podApplication Application can create SAS tunnels and communicate with applications running on the CableCARD.
signal.configured Application can call monitorConfiguredSignal().
properties Application permitted to read OCAP system properties.

Table 1: Monitor application permissions found in org.ocap.system.MonitorAppPermission.

Back to Article