To access One Identity Safeguard for Privileged Sessions (SPS) using the RPC API, the following requirements must be met:
-
Accessing the appliance via the RPC API must be enabled on the web interface. For details, see Enabling RPC API access to One Identity Safeguard for Privileged Sessions (SPS).
-
The appliance can be accessed using the SOAP protocol over authenticated HTTPS connections. The WSDL describing the available services is available at https://<ip-address-of-SPS>/rpc.php/<techversion>?wsdl. For details on the client libraries tested with SPS see RPC client requirements.
-
The user account used to access SPS via RPC must have read and write/perform rights for the Access RPC API privilege. This is required for every type of RPC access, even for read-only operations. Members of the api group automatically have this privilege. For details on managing user privileges, see Modifying group privileges.
|
Caution:
Each SPS release provides a separate API with a new API version number. You are recommended to use the SPS version 6.9.5 with the corresponding API version. Earlier versions are not supported |