Number of protected hosts in SPS 7

Hi,

The "Protected hosts" count no longer exists in the 7.0 and above release of SPS as there is no tracking of host-license anymore.

As per the 7.0 LTS release notes:

"SPS does not run an active license check for the ongoing traffic sessions and the license limits are evaluated on demand."

https://support.oneidentity.com/technical-documents/one-identity-safeguard-for-privileged-sessions/7.0%20lts/release-notes#TOPIC-1831296

Thanks!

So I don't understand the way to operate SPS under license. I have a license for 10 hosts. For testing, I also connected to servers that I don't need in production. An SNMP trap reports that a license has been reached during an RDP connection. RDP connection works. And I can't detect protected hosts.

Could you try the following:

Originally to reset the protected host count you would reset it using the following step:

To restart all traffic please log in to the Web UI as admin an navigate to Basic Settings -> System -> Traffic control -> All services and press Restart.

then connect to your 10 hosts that you wish to use in production and verify if the SNMP trap no longer appears for those 10 servers.

RDP works because the license is not enforcing a limit with the new version of SPS.

Thanks!

I did the reset as described about three times. After connecting with one new RDP, the notification comes again via SNMP and email. And as written in the release notes, SPS does not enforce the license, but the limit is evaluated on demand. Does that mean the limit is 10 simultaneous connections? Thank you for your time.

The limit would be to 10 specific hosts but not enforced anymore.

As a workaround may be you can disable the SNMP alert for "License limit reached" from Basic Settings > Alerts and Monitoring

Thanks!

Sorry, I found my mistake. I had a wrongly set trap for the license in the monitoring, and the monitoring also captured successful logins. So it was a false alarm.

I would still be interested in the use of licenses.

Sorry, I found my mistake. I had a wrongly set trap for the license in the monitoring, and the monitoring also captured successful logins. So it was a false alarm.

I would still be interested in the use of licenses.