Disable Secure Api Access; Access The Api With Ssh; Port Lockout - Polycom RealPresence Group Series Administrator's Manual

Procedure
» Do one of the following
• In the system web interface, go to Admin Settings > Security > Global Security > Access
and enable the Enable Legacy API Over SSH setting.
• In a system API session, enter sshenable true.

Disable Secure API Access

You can disable SSH for secure API access in the RealPresence Group Series system web interface or in
an API session.
Procedure
» Do one of the following:
• In the system web interface of the system, select Admin Settings > Security > Global
Security > Access and disable the Enable Legacy API Over SSH setting.
• In a system API session, enter sshenable false.

Access the API with SSH

To obtain secure access to the API, you must use an SSH client and connect to the IP address configured
for the RealPresence Group Series system on port 22. The system allows three attempts to enter correct
login credentials. The SSH client program closes after the third failed attempt.
To access the API with SSH:
Procedure
1. Enable remote access.
2. If necessary, enable external authentication.
3. Enable the SSH feature.
4. Start an SSH session using the system IP address and port 22.
5. When prompted, enter the remote access credentials.
For information on accessing the API, refer to the Polycom RealPresence Group Series Integrator
Reference Guide at Polycom

Port Lockout

Port lockout protects against brute-force attacks by temporarily locking the login port after a configurable
number of unsuccessful login attempts are made. Port lockout is supported only on the RealPresence
Group Series system web interface, and only Admin users are allowed to log in to the system web
interface. If external authentication is not in use, users can successfully log in to the system web interface
only by using the local Admin account credentials. However, when external authentication is in use, any
number of external accounts can be considered to be Admin users on the system. Failed logins to any of
these accounts, or to an unknown account, are all counted against the configured number allowed failed
login attempts to the system web interface.
The following is an example of how the port lockout feature works.
A system web interface is configured with these settings:
Polycom, Inc.
Support.
Securing the System
93