From One Identity Safeguard for Privileged Sessions (SPS) version 7.3, you can use the One Identity Safeguard Power BI Connector (Power BI Connector) to import and visualize audit data from SPS in the Power BI Desktop reporting application.
NOTE: Power BI Desktop integration using the Power BI Connector is only supported for SPS 7.3 and later feature versions.
For more information, see the One Identity Safeguard Power BI Connector Tutorial on the One Identity Support Portal.
Starting with One Identity Safeguard for Privileged Sessions (SPS) version 4 F2, certain parts and features of SPS can be configured using a REST API (Representational State Transfer Application Programming Interface). The REST server conforms to the Hypermedia as the Engine of Application State (HATEOAS).
The SPS REST API uses JSON over HTTPS. The REST server has a single entry point and all resources are available at paths (URLs) returned in the response for a request sent to the entry point. The only path that is guaranteed not to change is /api/authentication. Every other path should be reached by navigating the links returned.
The SPS REST API allows you to create, read, update and delete (CRUD) the configuration resources of SPS.
The user accessing the SPS REST API must have the REST server privilege. For details, see Modifying group privileges in the Administration Guide. For details on using the REST API, see REST API Reference Guide.
This section discusses common scenarios for One Identity Safeguard for Privileged Sessions (SPS).
If a protected server requires public-key authentication from the users, complete one of the following procedures.
In Configuring public-key authentication using local keys, One Identity Safeguard for Privileged Sessions (SPS) stores the public keys of the users and the private-public keypair used in the server-side connection locally on SPS.
In Configuring public-key authentication using an LDAP server and a fixed key, SPS receives the public keys of the users from an LDAP server and uses a locally-stored private-public keypair in the server-side connection.
In Configuring public-key authentication using an LDAP server and generated keys, SPS receives the public keys of the users from an LDAP server. SPS generates a keypair that is used in the server-side connection on-the-fly, then uploads the public key of this pair to the LDAP database. That way the server can authenticate SPS to the (newly generated) public key of the user.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center
