It may happen that you inadvertently lose the IPMI password of your One Identity Safeguard for Privileged Sessions (SPS). The following procedure describes how you can re-configure your SPS if you lose your IPMI password.
To apply the procedure outlined here, you will need physical access to a monitor and keyboard.
To configure the IPMI interface from the BIOS after losing your IPMI password
Shut down SPS.
Unplug the SPS physical appliance's power cord.
Wait 30 seconds.
Replug the power cord.
Restart the appliance.
Press the DEL button when the POST screen comes up while the appliance is booting.
Figure 321: POST screen during booting
In the BIOS, navigate to the IPMI page.
On the IPMI page, select BMC Network Configuration, and press Enter.
Figure 322: IPMI page > BMC Network Configuration option
On the BMC Network Configuration page, select Update IPMI LAN Configuration, press Enter, and select Yes.
Figure 323: BMC Network Configuration page > Update IPMI LAN Configuration
Stay on the BMC Network Configuration page, select Configuration Address Source, press Enter, and select Static.
Figure 324: BMC Network Configuration page > Configuration Address Source
Still on the BMC Network Configuration page, configure the Station IP Address, Subnet Mask, and Gateway IP Address individually.
Figure 325: BMC Network Configuration page > Station IP Address, Subnet Mask, Gateway IP Address
Press F4 to save the settings, and exit from the BIOS.
About a minute later, you will be able to log in on the IPMI web interface.
When using a TSA certificate generated with Windows Certificate Authority, you might see a similar error message:
Incomplete TSA response received, TSA HTTP server may be responding slowly; errno='Success (0)', timeout_seconds='30'
When generating the certificate, make sure that you do the following:
Optional Key Usage: If Key Usage is present, it must be digitalSignature and/or nonRepudiation. Other values are not permitted. Make sure that in Encryption, Allow key exchange without key encryption (key agreement) is selected.
In Encryption, do NOT select Allow key exchange only with key encryption (key encipherment), because it will result in errors.
When you specify user names in a User Principal Name (UPN) format (e-mail address as username) for an SPS-audited SSH connection, the connection is unsuccessful.
The connection is unsuccessful because SPS uses the '@' character in the username as inband destination selection. If this happens, the username is stripped from the domain part and the UPN suffix is interpreted as inband target. For example, if using firstname.lastname@example.org as username, the username for the connection will be 'test' and the inband destination is 'ema.il'. SPS interprets the last two '@' characters from the connection string, for example, username@my-inband-target@SPS.
To avoid this, you must use inband destination selection. By specifying the target host explicitly, you can prevent SPS to misinterpret the '@' character from UPN usernames.
You can join your One Identity Safeguard for Privileged Sessions (SPS) deployment to your One Identity Safeguard for Privileged Passwords (SPP) deployment. That way you can jointly use the features of the two deployments.
Both appliances provide different functionality. You can use them together or independently from each other.
Machine and account discovery
Password rotation and management
Advanced access request and approval workflows
A user portal and desktop application to initiate connections
Transparent or non-transparent interception of remote admin protocols (SSH, RDP, Telnet, Citrix ICA, and VNC)
Audit recording and video-like playback of sessions
Inband authentication of the monitored users independently from the target servers
Basic access control policy enforcement
Advanced search and reporting capabilities in the audit records
Built-in user behavior analytics for the recorded sessions (One Identity Safeguard for Privileged Analytics)
In the Passwords-initiated workflow, the users initiate sessions from SPP. In this workflow SPP uses SPS as a session-recording device.
You can use your browser or the One Identity Safeguard desktop client to request access from SPP and initiate the connection to the target server via SPS. SPP creates an access string for the user’s SSH or RDP client that allows these clients to connect to the target server via SPS, so SPS can audit and record the session. In this sense this workflow is nontransparent, the user must use a browser or the One Identity Safeguard desktop client.
This is what all SPS users who bought the Sessions Module use before SPP version 2.7.
Figure 326: Passwords-initiated (SPP-initiated) workflow
For details on configuring this workflow, see Configuring SPP for Passwords-initiated workflow.
In the Sessions-initiated workflow, the users initiate sessions from SPS. In this workflow SPS uses SPP as a credential store.
This workflow is transparent in the sense that you can connect to the target server or to SPS directly using your SSH or RDP client application. SPS authenticates these clients and communicates with SPP to get the password for the target server. It then uses that password to open the connection. Authentication happens on SPS, while authorization happens on SPP based on the user's entitlements.
This is what old and new users of standalone SPS are likely to prefer.
The usual SPP Access Requests workflows that SPP provides are supported:
Auto-approved access request
Approved/denied access request (similar to the four-eyes authorization feature of SPS)
Figure 327: Sessions-initiated (SPS-initiated) workflow