Security Handbook: Network-Enabled Devices, AOS v6.x.x
Security Handbook: Network-Enabled Devices, AOS v6.x.x
Security Handbook: Network-Enabled Devices, AOS v6.x.x
990-4910-001
Publication Date: December, 2013
Schneider Electric IT Corporation Legal Disclaimer
The information presented in this manual is not warranted by the Schneider Electric IT Corporation to be authoritative,
error free, or complete. This publication is not meant to be a substitute for a detailed operational and site specific
development plan. Therefore, Schneider Electric IT Corporation assumes no liability for damages, violations of codes,
improper installation, system failures, or any other problems that could arise based on the use of this Publication.
The information contained in this Publication is provided as is and has been prepared solely for the purpose of evaluating
data center design and construction. This Publication has been compiled in good faith by Schneider Electric IT
Corporation. However, no representation is made or warranty given, either express or implied, as to the completeness or
accuracy of the information this Publication contains.
IN NO EVENT SHALL SCHNEIDER ELECTRIC IT CORPORATION, OR ANY PARENT, AFFILIATE OR
SUBSIDIARY COMPANY OF SCHNEIDER ELECTRIC IT CORPORATION OR THEIR RESPECTIVE
OFFICERS, DIRECTORS, OR EMPLOYEES BE LIABLE FOR ANY DIRECT, INDIRECT,
CONSEQUENTIAL, PUNITIVE, SPECIAL, OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT
LIMITATION, DAMAGES FOR LOSS OF BUSINESS, CONTRACT, REVENUE, DATA, INFORMATION, OR
BUSINESS INTERRUPTION) RESULTING FROM, ARISING OUT, OR IN CONNECTION WITH THE USE
OF, OR INABILITY TO USE THIS PUBLICATION OR THE CONTENT, EVEN IF SCHNEIDER ELECTRIC
IT CORPORATION HAS BEEN EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
SCHNEIDER ELECTRIC IT CORPORATION RESERVES THE RIGHT TO MAKE CHANGES OR UPDATES
WITH RESPECT TO OR IN THE CONTENT OF THE PUBLICATION OR THE FORMAT THEREOF AT
ANY TIME WITHOUT NOTICE.
Copyright, intellectual, and all other proprietary rights in the content (including but not limited to software, audio, video,
text, and photographs) rests with Schneider Electric It Corporation or its licensors. All rights in the content not expressly
granted herein are reserved. No rights of any kind are licensed or assigned or shall otherwise pass to persons accessing this
information.
This Publication shall not be for resale in whole or in part.
Contents
Introduction.................................................................................. 1
Content and Purpose of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Types of User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Secure SHell (SSH) and Secure CoPy (SCP) for the Command Line Interface 6
Secure Sockets Layer (SSL) for the Web interface . . . . . . . . . . . . . . . 7
Creating and Installing Digital Certificates . . . . . . . . . . . . . . . . . . . . . . . 7
Choosing a Method for your System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
RADIUS ....................................................................................... 25
Supported RADIUS Functions and Servers . . . . . . . . . . . . . . . . . . . . . .25
Supported functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Supported RADIUS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configure the Management Card or Device . . . . . . . . . . . . . . . . . . . . 25
RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configure the RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Example using Service-Type Attributes . . . . . . . . . . . . . . . . . . . . . . . . 27
Examples using Vendor Specific Attributes . . . . . . . . . . . . . . . . . . . . 27
RADIUS Users file with VSAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Example with UNIX shadow passwords . . . . . . . . . . . . . . . . . . . . . . . . 28
Note: The Security Wizard can create security components for Management Cards or devices
running firmware version 6.x.x, 5.x.x, or 3.x.x. For information about using the Security Wizard
with a Management Card or device running firmware version 5.x.x, or 3.x.x. See the Security
Handbook provided on the Utility CD for that device (if applicable).
User Management
Types of User Accounts
The Network Management Card has three basic levels of access:
• A Super User: can use all of the management menus available in the Web interface and
all of the commands in the command line interface.
• Administrative User: can use all of the management menus available in the Web
interface and all of the commands in the command line interface.
• A Device User: can access the event log and data log (but cannot delete the contents of
either log), and can use the device-related menus and commands.
• Network-Only User: can only access information that is not device-related.
Note: A Super User is an Administrator account which is persistent and cannot be deleted, but
can still be enabled or disabled.
Note: Beginning with firmware version 6.x.x, multiple users can simultaneously be logged into
the device.
Security
Security Features
Protection of passwords and passphrases
Available methods For both SNMPv1 and SNMPv3, the host name restricts
(SNMPv1): access to the Network Management System (NMS) at that
• Community Name location only, and the NMS IP filters allow access only to the
• Host Name
NMSs specified by one of the IP address formats in the
• NMS IP filters
• Agents that can be following examples:
enabled or disabled • 159.215.12.1: Only the NMS at the IP address
• Four access 159.215.12.1.
communities • 159.215.12.255: Any NMS on the 159.215.12
• with read/write/disable segment.
capability
• 159.215.255.255: Any NMS on the 159.215
Available methods segment.
(SNMPv3): • 159.255.255.255: Any NMS on the 159 segment.
• Four User Profiles
• 0.0.0.0 or 255.255.255.255: Any NMS.
• Authentication through
an authentication • SNMPv3 has additional security features that
passphrase include the following:
• Encryption through a • An authentication passphrase to ensure that an
privacy passphrase NMS trying to access the Management Card or
• SHA or MD5 device is the NMS it claims to be.
authentication
• Encryption of data during transmission, with a
• AES or DES encryption
privacy passphrase required for encrypting and
algorithm
decrypting.
• NMS IP filters
Available methods: With FTP, the user name and password are transmitted as
• User name and plain text, and files are transferred without encryption. Use
password SCP to encrypt the user name and password and the files
• Selectable server port
being transferred, such as firmware updates, configuration
• Access protocols that
files, log files, Secure Sockets Layer (SSL) certificates, and
can be enabled or
disabled. Secure SHell (SSH) host keys. If you choose SCP as your file
• Secure CoPy (SCP) transfer protocol, enable SSH and disable FTP.
Available methods: In basic HTTP authentication mode, the user name and
• User name and password are transmitted base-64 encoded (with no
password encryption).
• Selectable server port SSL is available on Web browsers supported for use with the
• Web interface access Management Card or network-enabled device and on most
that can be enabled or Web servers. The Web protocol HyperText Transfer Protocol
disabled over Secure Sockets Layer (HTTPS) encrypts and decrypts
• Secure Sockets Layer page requests to the Web server and pages returned by the
(SSL) Web server to the user.
RADIUS
After installation and initial configuration of the Management Card or network-enabled device,
immediately change the user names and passwords from their defaults to unique user names
and passwords to establish basic security. The Super User can't have its user name changed,
but should be disabled once any additional Administrator accounts are created.
Port assignments
If Telnet, the FTP server, SSH/SCP, or the Web server uses a non-standard port, a user must
specify the port in the command line or Web address used to access the Management Card or
device. A non-standard port number provides an additional level of security. The ports are
initially set at the standard “well known ports” for the protocols. To increase security, reset the
ports to any unused port numbers from 5001 to 32768 for the FTP server and from 5000 to
32768 for the other protocols and servers. (The FTP server uses both the specified port and
the port one number lower than the specified port.)
All user names, passwords, and community names for SNMPv1 are transferred over the
network as plain text. A user who is capable of monitoring the network traffic can determine the
user names and passwords required to log on to the accounts of the command line interface or
Web interface of the Management Card or network-enabled device. If your network requires
the higher security of the encryption-based options available for the command line interface
and Web interface, disable SNMPv1 access or set its access to Read. (Read access allows
you to receive status information and use SNMPv1 traps.)
To disable SNMPv1 access on the Configuration tab, select Network on the top menu bar
and select Access under the SNMPv1 heading. Clear the Enable SNMPv1 access check box
and click Apply.
To set SNMPv1 access to Read, perform the following steps: On the Configuration tab select
Network. Select SNMPv1 and then Access Control. For each configured Network
Management System (NMS), click the community names and set the Access Type to Read.
Select Apply.
Authentication
You can choose security features for the Management Card or network-enabled device that
control access by providing basic authentication through user names, passwords, and IP
addresses, without using encryption. These basic security features are sufficient for most
environments in which sensitive data are not being transferred.
For encrypted communication when you use SNMP to monitor or configure the Management
Card or network-enabled device, choose SNMPv3. The privacy passphrase used with SNMPv3
user profiles ensures the privacy of the data (by means of encryption, using the AES or DES
encryption algorithm) that an NMS sends to or receives from the Management Card or device.
Secure SHell (SSH) and Secure CoPy (SCP) for the Command Line Interface
The Secure SHell protocol
SSH provides a secure mechanism to access computer consoles, or shells, remotely. The
protocol authenticates the server (in this case, the Management Card or network-enabled
device) and encrypts all transmissions between the SSH client and the server.
• SSH is a high-security alternative to Telnet. Telnet does not provide encryption.
• SSH protects the user name and password, which are the credentials for authentication,
from being used by anyone intercepting network traffic.
• To authenticate the SSH server (the Management Card or network-enabled device) to
the SSH client, SSH uses a host key unique to the SSH server. The host key is an
identification that cannot be falsified, and it prevents an invalid server on the network
from obtaining a user name and password by presenting itself as a valid server.
Note: For information on supported SSH client applications, see Telnet and Secure SHell
(SSH). To create a host key, see Create an SSH Host Key.
The Management Card or device supports SSH version 2, which provides protection from
attempts to intercept, forge, or change data during transmission.
• When you enable SSH, Telnet is automatically disabled.
• The interface, user accounts, and user access rights are the same whether you access
the command line interface through SSH or Telnet.
Secure CoPy
SCP is a secure file transfer application that you can use instead of FTP. SCP uses the SSH
protocol as the underlying transport protocol for encryption of user names, passwords, and
files.
• When you enable and configure SSH, you automatically enable and configure SCP. No
further configuration of SCP is needed.
• You must explicitly disable FTP. It is not disabled by enabling SSH. To disable FTP, on
the Configuration tab, select Network and then FTP Server. Clear the Enable check
box and click Apply.
SSL uses a digital certificate to enable the browser to authenticate the server (in this case, the
Management Card or device). The browser verifies the following:
• The format of the server certificate is correct.
• The expiration date and time of the server certificate have not passed.
• The DNS name or IP address specified when a user logs on matches the common name
in the server certificate.
• The server certificate is signed by a trusted certifying authority Each major browser
manufacturer distributes CA root certificates of the commercial Certificate Authorities in
the certificate store (cache) of its browser so that it can compare the signature on the
server certificate to the signature on a CA root certificate.
You can use the APC Security Wizard, provided on the Utility CD (if applicable), to create a
certificate signing request to an external Certificate Authority, or if you do not want to use an
existing Certificate Authority, you can create an APC root certificate to upload to the certificate
store (cache) of the browser. You can also use the Wizard to create a server certificate to
upload to the Management Card or device.
Note: See Creating and Installing Digital Certificates for a summary of how these certificates
are used. To create certificates and certificate requests, see Create a Root Certificate and
Server Certificates and Create a Server Certificate and Signing Request.
SSL also uses various algorithms and encryption ciphers to authenticate the server, encrypt
data, and ensure the integrity of the data, i.e., that it has not been intercepted and sent by
another server.
Note: Web pages that you have recently accessed are saved in the cache of your Web
browser and allow you to return to those pages without re-entering your user name and
password. Always close your browser session before you leave your computer unattended.
For network communication that requires a higher level of security than password encryption,
the Web interface of the Management Card or network-enabled device supports the use of
digital certificates with the Secure Sockets Layer (SSL) protocol. Digital certificates can
authenticate the Management Card or device (the server) to the Web browser (the SSL client).
Note: You can generate a 1024-bit key, or you can generate a 2048-bit key, which provides
complex encryption and a higher level of security.
• Method 1: Use the default certificate auto-generated by the Network Management Card
or network-enabled device.
• Method 2: Use the APC Security Wizard to create a CA certificate and a server
certificate.
• Method 3: Use the APC Security Wizard to create a certificate-signing request to be
signed by the root certificate of an external Certificate Authority and to create a server
certificate.
Note: You can also use Method 3 if your company or agency operates its own Certificate
Authority. Use the APC Security Wizard in the same way, but use your own Certificate Authority
in place of a commercial Certificate Authority.
Advantages:
• Before they are transmitted, the user name and password and all data to and from the
Management Card or device are encrypted.
• You can use this default server certificate to provide encryption-based security while you
are setting up either of the other two digital certificate options, or you can continue to use
it for the benefits of encryption that SSL provides.
Disadvantages:
• The Management Card or device takes up to 1 minute to create this certificate, and the
Web interface is not available during that time. (This delay occurs the first time you log on
after you enable SSL.)
• This method does not include the authentication provided by a CA certificate (a
certificate signed by a Certificate Authority) that Methods 2 and 3 provide. There is no CA
Certificate cached in the browser. Therefore, when you log on to the Management Card
or device, the browser generates a security alert, indicating that a certificate signed by a
trusted authority is not available, and asks if you want to proceed. To avoid this message,
you must install the default server certificate into the certificate store (cache) of the
browser of each user who needs access to the Management Card or device, and each
user must always use the fully qualified domain name of the server when logging on to
the Management Card or device.
Method 2: Use the APC Security Wizard to create a CA certificate and a server certificate
Advantages
Before they are transmitted, the user name and password and all data to and from
the Management Card or device are encrypted.
• You choose the length of the public key (RSA key) that is used for encryption when
setting up an SSL session (use 1024 bits, which is the default setting, or use 2048 bits to
provide complex encryption and a high level of security).
• The server certificate that you upload to the Management Card or device enables SSL to
authenticate that data are being received from and sent to the correct Management Card
or device. This provides an extra level of security beyond the encryption of the user
name, password, and transmitted data.
• The root certificate that you install to the browser enables the browser to authenticate the
server certificate of the Management Card or device to provide additional protection from
unauthorized access.
Method 3: Use the APC Security Wizard to create a certificate-signing request to be signed
by the root certificate of an external Certificate Authority and to create a server certificate.
Use the APC Security Wizard to create a request (a .csr file) to send to a Certificate Authority.
The Certificate Authority returns a signed certificate (a .crt file) based on information you
submitted in your request. You then use the APC Security Wizard to create a server certificate
(a .p15 file) that includes the signature from the root certificate returned by the Certificate
Authority. Upload the server certificate to the Management Card or device.
Note: You can also use Method 3 if your company or agency operates its own Certificate
Authority. Use the APC Security Wizard in the same way, but use your own Certificate Authority
in place of a commercial Certificate Authority.
Advantages
Before they are transmitted, the user name and password and all data to and from the
Management Card or device are encrypted.
• You have the benefit of authentication by a Certificate Authority that already has a signed
root certificate in the certificate cache of the browser. (The CA certificates of commercial
Certificate Authorities are distributed as part of the browser software, and a Certificate
Authority of your own company or agency has probably already loaded its CA certificate
to the browser store of each user’s browser.) Therefore, you do not have to upload a root
certificate to the browser of each user who needs access to the Management Card or
device.
• You choose the length of the public key (RSA key) that is used for setting up an SSL
session (use 1024 bits, which is the default setting, or use 2048 bits to provide complex
encryption and a high level of security).
• The server certificate that you upload to the Management Card or device enables SSL to
authenticate that data are being received from and sent to the correct Management Card
or device. This provides an extra level of security beyond the encryption of the user
name, password, and transmitted data.
• The browser matches the digital signature on the server certificate that you uploaded to
the Management Card or device with the signature on the CA root certificate that is
already in the browser’s certificate cache to provide additional protection from
unauthorized access.
Disadvantages
Setup requires the extra step of requesting a signed root certificate from a Certificate Authority.
• An external Certificate Authority may charge a fee for providing signed certificates.
Configuration:
Active Policy: Select an active policy from the available firewall policies.
Active Rules: Lists the individual rules that are being enforced based on the current active
policy.
Active Policy: Load a policy file (.fwl suffix) from a source external to this device.
An SSH host key authenticates the identity of the server (the Management Card or device)
each time an SSH client contacts that server. Each server with SSH enabled must have an
SSH host key on the server itself.
Note: If your Management Card or device is running firmware version 3.x.x, you must create
1024-bit RSA keys. For more information about configuring the security features of a
Management Card or device running firmware version 3.x.x, see the Security Handbook
provided on the Utility CD (if applicable) for that device.
Note: If you do not create and use SSL server certificates and SSH host keys with the APC
Security Wizard, the Management Card or device generates 2048-bit RSA keys.
Only APC server management and key management products can use server certificates, host
keys, and CA root certificates created by the APC Security Wizard. These files will not work
with products such as OpenSSL® and Microsoft® Internet Information Services (IIS).
The Procedure
Create the CA root certificate
• If the APC Security Wizard is not already installed on your computer, run the installation
program (APC Security Wizard.exe) by clicking the link Security Wizard, then Install
the Wizard, in the interface of the Utility CD (if applicable) for the Management Card or
device.
• On the Windows Start menu, select Programs, then APC Security Wizard.
• On the screen labeled Step 1, select CA Root Certificate as the type of file to create,
and then select the length of the key to generate (use 1024 bits, which is the default
setting, or use 2048 bits to provide complex encryption and a high level of security).
• Enter a name for this file, which will contain the Certificate Authority’s public root
certificate and private key. The file must have a .p15 suffix and, by default, will be created
in the installation folder C:\Program Files\American Power Conversion\APC Security
Wizard.
• On the screen labeled Step 2, provide the information to configure the CA root certificate.
The Country and Common Name fields are the only required fields. For the Common
Name field, enter an identifying name of your company or agency. Use only
alphanumeric characters, with no spaces.
Note: By default, a CA root certificate is valid for 10 years from the current date and time, but
you can edit the Validity Period Start and Validity Period End fields.
• On the next screen, review the summary of the certificate. Scroll downward to view the
certificate’s unique serial number and fingerprints. To make any changes to the
information you provided, click back. Revise the information.
Note: The certificate’s subject information and the certificate’s issuer information should be
identical.
• The last screen verifies that the certificate was created and displays information you
need for the next tasks:
a. The location and name of the .p15 file that you will use to sign the server
certificates.
b. The location and name of the .crt file, which is the CA root certificate to load into
the browser of each user who needs to access the Management Card or device.
• On the next screen, review the summary of the certificate. Scroll downward to view the
certificate’s unique serial number and fingerprints. To make any changes to the
information you provided, click Back. Revise the information.
• The last screen verifies that the certificate has been created and instructs you to load the
server certificate to the Management Card or device. It displays the location and name of
the Server Certificate, which has a .p15 file suffix and contains the private key and public
root certificate of the Management Card or device.
• On the next screen, review the summary of the certificate. Scroll downward to view the
unique serial number and fingerprints of the certificate. To make any changes to the
information you provided, click Back. Revise the information.
Note: The certificate’s subject information and the certificate’s issuer information should be
identical.
• The last screen verifies that the certificate signing request was created and displays the
location and name of the file, which has a .csr extension.
• Send the certificate signing request to an external Certificate Authority, either a
commercial Certificate Authority or, if applicable, a Certificate Authority managed by your
own company or agency.
Note: See the instructions provided by the Certificate Authority regarding the signing and
issuing of server certificates.
• On the Windows Start menu, select Programs, then APC Security Wizard.
• On the screen labeled Step 1, select Import Signed Certificate.
• Browse to and select the signed server certificate that you received from the external
Certificate Authority. The file has a .cer or .crt suffix.
• Browse to and select the file you created in step 4 of the task Create the Certificate
Signing Request (CSR). This file has a .p15 extension, contains the private key of the
Management Card or device, and, by default, is in the installation folder C:\Program
Files\American Power Conversion\APC Security Wizard.
• Specify a name for the output file that will be the signed server certificate that you upload
to the management card or device. The file must have a .p15 suffix.
• Click Next to generate the server certificate. Issuer Information on the summary screen
confirms that the external Certificate Authority signed the certificate.
• The last screen verifies that the certificate has been created and instructs you to load the
server certificate to the Management Card or device. It displays the location and name of
the server certificate, which has a .p15 file extension and contains the private key of the
Management Card or device and the public key obtained from the .cer or .crt file.
• Use the APC Security Wizard to create a host key, which is encrypted and stored in a file
with the .p15 suffix.
• Load the host key onto the Management Card or device.
Telnet for basic access. Telnet provides the basic security of authentication by user name and
password, but not the high-security benefits of encryption.
SSH for high-security access. If you use the high security of SSL for the Web interface, use
Secure SHell (SSH) for access to the command line interface. SSH encrypts user names,
passwords and transmitted data.
The interface, user accounts, and user access rights are the same whether you access the
command line interface through SSH or Telnet, but to use SSH, you must first configure SSH
and have an SSH client program installed on your computer.
• On the Configuration tab of the We interface, select Network on the top menu bar, and
select Access under the Console heading.
• Configure the port settings for Telnet and SSH.
Note: For information on the extra security a non-standard port provides, see Port
assignments.
• Select: Configuration > Network > Console > SSH Host Key. specify a host key file
previously created with the APC Security Wizard, and load it to the Management Card or
device.
If you do not specify a host key file here, if you install an invalid host key, or if you enable SSH
with no host key installed, the Management Card or device generates an RSA host key of 2048
bits. For the Management Card or device to create a host key, it must reboot. The Management
Card or device can take up to 1 minute to create this host key, and SSH is not accessible
during that time.
Note: Alternatively, from a command line interface such as the command prompt on Windows
operating systems, you can use FTP or Secure CoPy (SCP) to transfer the host key file.
• Display the fingerprint of the SSH host key for SSH version 2. Most SSH clients display
the fingerprint at the start of a session. Compare the fingerprint displayed by the client to
the fingerprint that you recorded from the Web interface or command line interface of the
Management Card or device.
Note: See Creating and Installing Digital Certificates to choose among the several methods for
using digital certificates.
• On the Configuration tab, select Network on the top menu bar and Access under the
Web tab.
• Enable either HTTP or HTTPS and configure the ports that each of the two protocols will
use. Changes take effect the next time you log on. When SSL is activated, your browser
displays a small lock icon.
Note: For information on the extra security a non-standard port provides, see Port
assignments.
• Select: Configuration > Network > Web > SSL Certificate to determine whether a
server certificate is installed on the Management Card or device. If a certificate was
created with the APC Security Wizard but is not installed:
a. In the Web interface, browse to the certificate file and upload it to the Management
Card or device.
b. Alternatively, use the Secure CoPy (SCP) protocol or FTP to upload the certificate
file to the Management Card or device.
Note: Creating and uploading a server certificate in advance reduces the time required to
enable HTTPS. If you enable HTTPS with no server certificate loaded, the Management Card
or device creates one when it reboots. The Management Card or device can take up to 1
minute to create the certificate, and the SSL server is unavailable during that time.
Note: A certificate that the Management Card or device generates has some limitations. See
Method 1: Use the default certificate auto-generated by the Network Management Card or
network-enabled device.
• If a valid digital server certificate is loaded, the Status field displays the link Valid
Certificate. Click the link to display the parameters of the certificate.
Issued on: The date and time at which the certificate was
Validity: issued.Expires on: The date and time at which the certificate
expires.
On the Configuration tab, select Security on the top menu bar. Then, under Remote Users
on the left navigation menu, select authentication to define an authentication method:
• Local Authentication Only: RADIUS is disabled. Local authentication is enabled.
• RADIUS, then Local Authentication: Both RADIUS and local authentication are
enabled. Authentication is requested from the RADIUS server first; local authentication is
used only if the RADIUS server fails to respond.
• RADIUS Only: RADIUS is enabled. Local authentication is disabled.
Note: If RADIUS Only is selected, and the RADIUS server is unavailable, improperly identified,
or improperly configured, remote access is unavailable to all users. You must use a serial
connection to the command line interface and change the RADIUS access setting to local or
radiusLocal to regain access. For example, the command to change the access setting to
local would be: radius -a local.
RADIUS
To configure RADIUS, on the Configuration tab, select Security on the top menu bar. Then,
under Remote Users on the left navigation menu, select RADIUS.
Skip Test and Apply Do not test the RADIUS server path.
If two configured servers are listed and RADIUS, then Local Authentication or RADIUS Only
is the enabled authentication method, you can change which RADIUS server will authenticate
users by clicking the Switch Server Priority button.
• Add the IP address of the Management Card or device to the RADIUS server client list
(file).
• Users must be configured with Service-Type attributes unless Vendor Specific Attributes
(VSAs) are defined instead. If no Service-Type attribute is configured, the user has read-
only access (to the Web interface only). The two acceptable values for Service-Type are
Administrative-User (6), which gives the user Administrator permissions, and Login-User
(1), which gives the user Device permissions.
Note: See your RADIUS server documentation for information about the RADIUS users file.
• Types of user accounts for information on the three basic user permission
levels (Super User/Administrator, Device User, and Read-Only User). If your APC
device has an additional user account type, e.g., outlet user for a Switched
Rack PDU, see the User’s Guide provided with your device for information
on the additional account type
• Supported RADIUS servers for information on RADIUS servers tested and
supported by APC.
© 2013 Schneider Electric, APC and the APC logo are owned by Schneider Electric Industries S.A.S., or its affiliated
companies. All other trademarks are property of their respective owners.
990-4910-001 12/2013