RXOP development often requires an "ACL file" which allows the RXOP application access to specific internal Service Program (SP) settings.
Since there are hundreds of SP settings that are accessible via RXOP, RiDP requires that RXOP application vendors request the minimal settings required for the application. An ACL request is simply a formatted pure text file (i.e., not a UTF-8 or binary file) containing key-value pairs that provides input to an automated process that will generate the ACL file used by the application.
An example file might look like this:
# Date: 13/12/2022
# Incident: #xxxx
# Company: ABC Company
# Product name: ABC appllication
# Product ID: 1711276xxx (SmartSDK), 403xxxxxx (SDK/J)
# Purpose: Test device for SmartSDK and SDK/J applications
#
# Enable custom authentication
#
Service Program: ACCESS_CONTROL__SDK_CERTIFICATION_DEVICE
Permissions (read): yes
Permissions (write): yes; values:
#
# Enable user administrator authentication
#
Service Program: ADMINISTRATOR_AUTHENTICATION_MANAGEMENT__USER_ADMINISTRATOR_AUTHENTICATION_SETTING
Permissions (read): yes
Permissions (write): yes; values:
#
# Enable machine administrator authentication
#
Service Program: ADMINISTRATOR_AUTHENTICATION_MANAGEMENT__MACHINE_ADMINISTRATOR_AUTHENTICATION_SETTING
Permissions (read): yes
Permissions (write): yes; values:
### Support All Devices ###
Device:ALL
Please note the following:
- A hash (
#) character at the beginning of a line is ignored and is used for human-readable comments Service Programis the name of the SP formatted exactly as the constant Strings found in the RXOP library Java documentation for the SPPermissions (read)should always have a value ofyes(without any trailing non-whitespace characters)Permissions (write)should always have a value ofyes; values:(without any trailing non-whitespace characters, but always include the trailing colon)
This file can be committed to source code control along with the application source as reference for future requests.
FAQ Subject
Faq Category