Configuring Global System Options
From the
System Administration > Configuration > Global System Options
pages, you can view these options:
Configuring TACACS+ Settings
Use the TACACS+ Settings page to configure TACACS+ runtime characteristics.
Select
System Administration > Configuration > Global System Options > TACACS+ Settings.
The TACACS+ Settings page appears as described in
Table 18-1
:
Table 18-1 TACACS+ Settings
|
|
Port to Listen
|
Port number on which to listen. By default, the port number is displayed as 49. ACS 5.8 allows you to edit this field. You can configure the TACACS+ port with number 49 and numbers ranging from 1024 to 65535. However, ACS does not allow the port numbers that are already assigned to other ports. This operation restarts the ACS runtime and all registered instances.
|
Connection Timeout
|
Number of minutes before the connection times out.
|
Session Timeout
|
Number of minutes before the session times out.
|
Maximum Packet Size
|
Maximum packet size (in bytes).
|
Single Connect Support
|
Check to enable single connect support.
|
Internal User Authorization Cache
|
Note This option is available from ACS 5.8 patch 7 or later.
The cache mechanism is applicable only for TACACS+ authorization flow for internal users.
When this option is enabled, the username and user specific attributes read from the internal database are stored in the cache after the first successful authorization request, for the specified time period. You can also specify the time for which the user details are to be stored in the cache. The valid range is from 1 to 5 minutes.
|
|
Username Prompt
|
Text string to use as the username prompt.
|
Password Prompt
|
Text string to use as the password prompt.
|
|
Enable TELNET Change Password
|
Choose this option if you want to provide an option to change password during a TELNET session.
|
Prompt for Old Password
|
Text string to use as the old password prompt.
|
Prompt for New Password
|
Text string to use as the new password prompt.
|
Prompt for Confirm Password
|
Text string to use as the confirm password prompt.
|
Disable TELNET Change Password
|
Choose this option if you do not want change password during a TELNET session.
|
Message when Disabled
|
Message that is displayed when you choose the Disable TELNET Change Password option.
|
Configuring EAP-TLS Settings
Use the EAP-TLS Settings page to configure EAP-TLS runtime characteristics.
Choose
System Administration > Configuration > Global System Options > EAP-TLS Settings.
The EAP-TLS Settings page appears as described in
Table 18-2
:
Table 18-2 EAP-TLS Settings
|
|
|
Enable EAP-TLS Session Resume
|
Check this check box to support abbreviated reauthentication of a user who has passed full EAP-TLS authentication.
This feature provides reauthentication of the user with only an SSL handshake and without the application of certificates. EAP-TLS session resume works only within the specified EAP-TLS session timeout value.
|
EAP-TLS Session Timeout
|
Enter the number of seconds before the EAP-TLS session times out. The default value is
7200 seconds.
|
|
Master Key Generation Period
|
The value is used to regenerate the master key after the specified period of time. The default is one week.
|
Revoke
|
Click
Revoke
to cancel all previous master keys. This operation should be used with caution.
If the ACS node is a secondary node, the Revoke option is disabled.
|
Configuring PEAP Settings
Use the PEAP Settings page to configure PEAP runtime characteristics.
Choose
System Administration > Configuration > Global System Options > PEAP Settings.
The PEAP Settings page appears as described in
Table 18-3
:
Table 18-3 PEAP Settings
|
|
Enable PEAP Session Resume
|
When checked, ACS caches the TLS session that is created during phase one of PEAP authentication, provided the user successfully authenticates in phase two of PEAP. If a user needs to reconnect and the original PEAP session has not timed out, ACS uses the cached TLS session, resulting in faster PEAP performance and a lessened AAA server load.
You must specify a PEAP session timeout value for the PEAP session resume features to work.
|
PEAP Session Timeout
|
Enter the number of seconds before the PEAP session times out. The default value is 7200 seconds.
|
Enable Fast Reconnect
|
Check to allow a PEAP session to resume in ACS without checking user credentials when the session resume feature is enabled.
|
Related Topics
Configuring Security Settings
Note This feature works only after installing ACS 5.8 patch 4 or later.
Use the Security Settings page to configure HTTPS Security Settings and Runtime Protocols Security Settings.
Choose
System Administration > Configuration > Global System Options > Security Settings.
The Security Settings page appears as described in
Table 18-4
:
Table 18-4 Security Settings
|
|
|
Enable TLS 1.0 for https access
|
Check this check box to allow communication with the browser through TLS 1.0/1.1/1.2. You need to make sure that the browser is enabled with TLS 1.0 before enabling this option. This option is disabled by default. If this check box is not checked, ACS allows communication with the browser through TLS 1.1/1.2.
|
Runtime Protocols Security Settings
|
Enable TLS 1.0 only for legacy clients
|
Check this check box to enable TLS 1.0 only for legacy clients for EAP-TLS, PEAP, and EAP-FAST protocols and for legacy secure services. This option is enabled by default.
|
Enable SHA-1 only for legacy clients
|
Check this check box to enable SHA-1 cipher suites only for legacy clients for EAP-TLS, PEAP, and EAP-FAST protocols and for legacy secure services. This option is enabled by default.
|
Configuring HTTP Proxy Settings for CRL Requests
ACS 5.8 introduces proxy settings for CRL downloads to proxy requests and responses from the CRL distribution server for greater security. ACS provides an option for administrators to enable the proxy settings on the HTTP Proxy Settings page for ACS to communicate with the CRL distribution server through the configured proxy server. The proxy server receives the request from ACS and forwards it to the CRL distribution server. The CRL distribution server, upon receiving the request from the proxy, processes it and forwards the CRLs to the proxy server. The proxy server receives the CRLs from the CRL distribution server and forwards them to ACS.
Use the HTTP Proxy Settings page to configure the HTTP Proxy for CRL requests from ACS.
Choose
System Administration > Configuration > Global System Options > HTTP Proxy Settings.
The HTTP Proxy Settings page appears as described in
Table 18-3
:
Table 18-5 HTTP Proxy Settings
|
|
|
Enable HTTP Proxy
|
Check the Enable HTTP Proxy check box for ACS to communicate with the CRL distribution URL through a proxy server.
|
Proxy Address
|
Enter the proxy IP address or DNS-resolvable hostname to be used as a proxy server for retrieving CRLs from an external CRL distribution server. ACS communicates with the configured proxy server for CRL information. The proxy server forwards the request to the CRL distribution server URL. The proxy server receives the revocation list and forwards it to ACS.
|
Proxy Port
|
Enter the port number through which the proxy traffic travels to and from ACS.
|
Related Topics
Adding a Certificate Authority
Configuring EAP-FAST Settings
Use the EAP-FAST Settings page to configure EAP-FAST runtime characteristics.
Choose
System Administration > Configuration > Global System Options > EAP-FAST > Settings.
The EAP-FAST Settings page appears as described in
Table 18-6
:
Table 18-6 EAP-FAST Settings
|
|
|
Authority Identity Info Description
|
User-friendly string that describes the ACS server that sends credentials to a client. The client can discover this string in the Protected Access Credentials Information (PAC-Info) Type-Length-Value (TLV). The default value is
Cisco Secure ACS.
|
Master Key Generation Period
|
The value is used to encrypt or decrypt and sign or authenticate PACs. The default is one week.
|
|
Revoke
|
Click
Revoke
to revoke all previous master keys and PACs. This operation should be used with caution.
If the ACS node is a secondary node, the Revoke option is disabled.
|
Generating EAP-FAST PAC
Use the EAP-FAST Generate PAC page to generate a user or machine PAC.
Step 1 Choose
System Administration > Configuration > Global System Options > EAP-FAST > Generate PAC.
The Generate PAC page appears as described in
Table 18-7
:
Table 18-7 Generate PAC
|
|
Tunnel PAC
|
Select to generate a tunnel PAC.
|
Machine PAC
|
Select to generate a machine PAC.
|
Identity
|
Specifies the username or machine name presented as the “inner username” by the EAP-FAST protocol. If the Identity string does not match that username, authentication will fail.
|
PAC Time To Live
|
Enter the equivalent maximum value in seconds, minutes, hours, days, weeks, months, and years. Enter a positive integer.
|
Password
|
Enter the password.
|
Step 2 Click
Generate PAC
.
Configuring RSA SecurID Prompts
You can configure RSA prompts for an ACS deployment. The set of RSA prompts that you configure is used for all RSA realms and ACS instances in a deployment. To configure RSA SecurID Prompts:
Step 1 Choose
System Administration > Configuration > Global System Options > RSA SecurID Prompts
.
The RSA SecurID Prompts page appears.
Step 2 Modify the fields described in
Table 18-8
.
Table 18-8 RSA SecurID Prompts Page
|
|
Passcode Prompt
|
Text string to request for the passcode. The default value is “Enter PASSCODE:”.
|
Next Token Prompt
|
Text string to request for the next token. The default value is “Enter Next TOKENCODE:”.
|
Choose PIN Type Prompt
|
Text string to request the PIN type. The default value is “Do you want to enter your own pin?”.
|
Accept System PIN Prompt
|
Text string to accept the system-generated PIN. The default value is “ARE YOU PREPARED TO ACCEPT A SYSTEM-GENERATED PIN?”.
|
For the two PIN entry prompts below, if the prompt contains the following strings, they will be substituted as follows:
-
{MIN_LENGTH}—will be replaced by the minimum PIN length configured for the RSA realm.
-
{MAX_LENGTH}—will be replaced by the maximum PIN length configured for the RSA realm.
-
/x/—to cancel the new PIN procedure.
|
Alphanumeric PIN Prompt
|
Text string for requesting an alphanumeric PIN.
|
Numeric PIN Prompt
|
Text string for requesting a numeric PIN.
|
Re-Enter PIN Prompt
|
Text string to request the user to re-enter the PIN. The default value is “Reenter PIN:”.
|
Step 3 Click
Submit
to configure the RSA SecurID Prompts.
Managing Dictionaries
The following tasks are available when you select
System Administration > Configuration > Dictionaries
:
Viewing RADIUS and TACACS+ Attributes
The RADIUS and TACACS+ Dictionary pages display the available protocol attributes in these dictionaries:
-
RADIUS (IETF)
-
RADIUS (Cisco)
-
RADIUS (Microsoft)
-
RADIUS (Ascend)
-
RADIUS (Cisco Airespace)
-
RADIUS (Cisco Aironet)
-
RADIUS (Cisco BBSM)
-
RADIUS (Cisco VPN 3000)
-
RADIUS (Cisco VPN 5000)
-
RADIUS (Juniper)
-
RADIUS (Nortel [Bay Networks])
-
RADIUS (RedCreek)
-
RADIUS (US Robotics)
-
TACACS+
To view and choose attributes from a protocol dictionary, select
System Administration > Configuration > Dictionaries > Protocols;
then choose a dictionary.
The Dictionary page appears with a list of available attributes as shown in
Table 18-9
:
Table 18-9 Protocols Dictionary Page
|
|
Attribute
|
Name of the attribute.
|
ID
|
(RADIUS only) The VSA ID.
|
Type
|
Data type of the attribute.
|
Direction
|
(RADIUS only) Specifies where the attribute is in use: in the request, in the response, or both. Single or bidirectional authentication.
|
Multiple Allowed
|
(RADIUS only) Multiple attributes are allowed. Attributes that specify
multiple allowed
can be used more than once in one request or response.
|
Use the arrows to scroll through the attribute list.
ACS 5.8 also supports RADIUS vendor-specific attributes (VSAs). A set of predefined RADIUS VSAs are available. You can define additional vendors and attributes from the ACS web interface. You can create, edit, or delete RADIUS VSAs.
After you have defined new VSAs, you can use them in policies, authorization profiles, and RADIUS token servers in the same way as predefined VSAs. For more information, see:
Creating, Duplicating, and Editing RADIUS Vendor-Specific Attributes
Vendor-specific attributes (VSAs) allow vendors to create extensions to the RADIUS attributes. Vendors are assigned a specific vendor numbers. VSAs are attributes that contain subattributes. ACS 5.8 allows you to create, duplicate, and edit RADIUS VSAs.
To Create, edit, and duplicate RADIUS VSAs:
Some of the internally used attributes cannot be modified. You cannot modify an attribute’s type if the attribute is used by any policy or policy element.
Step 1 Choose
System Administration > Configuration > Dictionaries > Protocols > RADIUS VSA
.
Step 2 Do one of the following:
-
Click
Create
.
-
Check the check box the RADIUS VSA that you want to duplicate, and click
Duplicate
.
-
Check the check box the RADIUS VSA that you want to edit, and click
Edit
.
The RADIUS VSA page appears. Modify the fields as described in
Table 18-10
.
Table 18-10 RADIUS VSA - Create, Duplicate, Edit Page
|
|
Attribute
|
Name of the RADIUS VSA.
|
Description
|
(Optional)
A brief description of the RADIUS VSA.
|
Vendor ID
|
ID of the RADIUS vendor.
|
Attribute Prefix
|
(Optional)
Prefix that you want to prepend to the RADIUS attribute so that all attributes for the vendor start with the same prefix.
|
Use Advanced Vendor Options
|
Vendor Length Field Size
|
Vendor length field of 8 bits for specifying the length of the VSA. Choose the vendor length of the VSA. Valid options are 0 and 1. The default value is 1.
|
Vendor Type Field Size
|
Vendor type field of 8 bits. Choose the vendor type of the VSA. Valid options are 1, 2, and 4. The default value is 1.
|
Step 3 Click
Submit
to save the changes.
Related Topics
Viewing RADIUS and TACACS+ Attributes
Importing RADIUS Vendors and Vendor-Specific Attributes
ACS 5.8 supports importing RADIUS vendors and RADIUS vendor-specific attributes (VSAs). In ACS 5.8, you have the option to import the RADIUS vendors and RADIUS VSAs from a text file. This text file is based on the Free RADIUS format. For more information on the Free RADIUS format, see
http://linux.die.net/man/5/dictionary
. The ACS 5.8 web interface provides you the option to download the Import template. You need to enter the vendor and its attributes in the same file.
Note ACS supports A-Z, a-z, 0-9, -, _, and / characters for use in the Import file.
Each RADIUS vendor should have a unique vendor ID. You cannot provide different IDs for the same vendor. Therefore, when you import vendors and VSAs, if the vendor name or attribute is already present in ACS, then the import operation fails with errors. In this case, you need to delete that particular vendor, or both the vendors and its attributes, and then re-import the file. ACS displays an appropriate error message and stops the import operation if the file format is wrong or any unsupported characters are present in the file.
Figure 18-1 Example for RADIUS Vendor and VSAs in Free RADIUS File
The # key at the beginning of a line indicates that the line is a comment line. The keyword VENDOR at the beginning of a line indicates that the line has vendors. The keyword ATTRIBUTE at the beginning of a line indicates that the line has VSAs. The value of a VSA should start with the vendor name. For instance, if the vendor name is Cisco, then the attribute value is cisco-fax-message-id.
When an attribute is of the Enumeration type, you need to specify the Enumeration name and Enumeration ID in the Free RADIUS file.
Table 18-11
displays the attributes types that are supported in a Free RADIUS text file and their mapping with the attribute types in ACS.
Table 18-11 Attributes Mapping Between Free RADIUS File and ACS
Attribute Type in Free RADIUS File
|
Attribute Type in ACS Web Interface
|
String
|
String
|
Octets
|
HexString
|
IP address
|
IPv4 address
|
Integer
|
Integer/Enumeration
|
The edit operation, delete operation, directions, and multi-value attributes are not supported when you import RADIUS vendors and RADIUS VSAs. You need to manually perform these operations after importing the vendors and VSAs.
To import RADIUS vendors and RADIUS VSAs:
Step 1 Choose
System Administration > Configuration > Dictionaries > Protocols > RADIUS VSA
.
The RADIUS VSA page appears.
Step 2 Click Import.
The Import dialog box appears.
Step 3 Click Download Template to download the import file template from the ACS web interface and save it to your client machine.
Step 4 Enter the RADIUS vendors and RADIUS VSAs in the specified format and save them.
Step 5 Click Browse to browse to the location of the Free RADIUS format file that has the RADIUS vendors and RADIUS VSAs and is ready to be imported.
Step 6 Click Start Import to start the import operation.
The RADIUS vendors and RADIUS VSAs are imported. ACS displays the log messages in a pop-up window.
Related Topics
Viewing RADIUS and TACACS+ Attributes
Creating, Duplicating, and Editing RADIUS Vendor-Specific Subattributes
To create, duplicate, and edit RADIUS vendor-specific subattributes:
Step 1 Choose
System Administration > Configuration > Dictionaries > Protocols > RADIUS > RADIUS VSA
.
You can alternatively choose the RADIUS VSA from the navigation pane.
Step 2 Do one of the following:
-
Click
Create
to create a subattribute for this RADIUS VSA.
-
Check the check box the RADIUS VSA that you want to duplicate, then click
Duplicate
.
-
Check the check box the RADIUS VSA that you want to edit, then click
Edit
.
-
Check the check box a RADIUS Vendor and click Show Vendor Attributes to view the VSAs of this Vendor.
The RADIUS VSA subattribute create page appears.
Step 3 Complete the fields described in
Table 18-12
.
Table 18-12 Creating, Duplicating, and Editing RADIUS Subattributes
|
|
|
Attribute
|
Name of the subattribute. The name must be unique.
|
Description
|
(Optional) A brief description of the subattribute.
|
|
Vendor Attribute ID
|
Enter the vendor ID field for the subattribute. This value must be unique for this vendor.
|
Direction
|
Specifies where the attribute is in use: in the request, in the response, or both. Single or bidirectional authentication.
|
Multiple Allowed
|
Multiple attributes are allowed. Attributes that specify
multiple allowed
can be used more than once in one request or response.
|
Include attribute in the log
|
Check this check box to include the subattribute in the log. For sensitive attributes, you can uncheck this check box so to they are not logged.
|
|
Attribute Type
|
Type of the attribute. Valid options are:
-
String
-
Unsigned Integer 32
-
IPv4 Address
-
HEX String
-
Enumeration—If you choose this option, you must enter the ID-Value pair
You cannot use attributes of type HEX String in policy conditions.
|
ID-Value
|
(Optional)
For the Enumeration attribute type only.
-
ID—Enter a number from 0 to 999.
-
Value—Enter a value for the ID.
-
Click
Add
to add this ID-Value pair to the ID-Value table.
To edit, replace, and delete ID-Value pairs:
-
Select the ID-Value pair from the ID-Value table.
-
Click
Edit
to edit the ID and Value fields. Edit the fields as required.
-
Click
Add
to add a new entry after you modify the fields.
-
Click
Replace
to replace the same entry with different values.
-
Click
Delete
to delete the entry from the ID-Value table.
|
|
Add Policy Condition
|
Check this check box to enter a policy condition in which this subattribute will be used.
|
Policy Condition Display Name
|
Enter the name of the policy condition that will use this subattribute.
|
Step 4 Click
Submit
to save the subattribute.
Configuring Identity Dictionaries
This section contains the following topics:
Creating, Duplicating, and Editing an Internal User Identity Attribute
To create, duplicate, and edit an internal user identity attribute:
Step 1 Select
System Administration > Configuration > Dictionaries > Identity > Internal Users
.
The Attributes list for the Internal Users page appears.
Step 2 Perform one of these actions:
-
Click
Create
.
-
Check the check box the attribute that you want to duplicate and click Duplicate.
-
Click the attribute name that you want to modify; or, check the check box for the name and click
Edit
.
The Identity Attribute Properties page appears.
Step 3 Modify the fields in the Identity Attributes Properties page as required. See Configuring Internal Identity Attributes for field descriptions.
Step 4 Click
Submit
.
The internal user attribute configuration is saved. The Attributes list for the Internal Users page appears with the new attribute configuration.
Related Topics
Configuring Internal Identity Attributes
Table 18-13
describes the fields in the internal <
users
|
hosts
> identity attributes.
Table 18-13 Identity Attribute Properties Page
|
|
|
Attribute
|
Name of the attribute.
|
Description
|
Description of the attribute.
|
|
Attribute Type
|
(Optional) Use the drop-down list box to choose an attribute type. Valid options are:
-
String—Populates the Maximum Length and Default Value fields in the page. When you select String as the attribute type and enter a non-null value for a user, the user is authenticated against the ID store with the name that matches the already set value, for the attribute that is shown in the user details (ACS-RESERVED-Authen-ID-Store).
-
Unsigned Integer 32—Populates the Valid Range From and To fields in the page.
-
IP Address—Populates the Default Value field in the page. This can be either IPv4 or IPv6 addresses.
-
Boolean—Populates the Default Value check box in the page. When you set the value of the Boolean attribute as true, it overrides the global settings for the password expiration policy and deactivates the policy (ACS-RESERVED-Never-Expired).
-
Date—Populates the Default Value field and calendar icon in the page.
-
Enumeration—Populates the ID and Value fields and the Add, Edit, Replace, and Delete buttons.
|
Maximum Length
|
(Optional)
For the String attribute type only
. Enter the maximum length of your attribute. The valid range is from 1 to 256. (Default = 32)
|
Value Range
|
(Optional)
For the Unsigned Integer attribute type only
.
-
From—Enter the lowest acceptable integer value. The valid range is from 0 to 2^31-1 (2147483647). This value must be smaller than the Valid Range To value.
-
To—Enter the highest acceptable integer value. The valid range is from 0 to 2^31-1 (2147483647). This value must be larger than the Valid Range From value.
|
Default Value
|
Enter the default value for the appropriate attribute:
-
String—Up to the maximum length. (Follow the UTF-8 standard.) You can use the letters a to z, A to Z, and the digits 0 to 9.
-
Unsigned Integer 32—An integer in the range from 0 to 2^31-1 (2147483647).
-
IP Address —Enter the IP address you want to associate with this attribute, in this format:
–
IPv4 address—x.x.x.x
, where
x.x.x.x
is the IPv4 address (no subnet mask)
– IPv6 address—
x:x:x:x:x:x:x:x, where x:x:x:x:x:x:x:x is the IPv6 address (no subnet mask)
-
Date—Click the calendar icon to display the calendar pop-up and select a date.
-
Boolean Value—Select True or False.
|
ID-Value
|
(Optional)
For the Enumeration attribute type only.
-
ID—Enter a number from 0 to 999.
-
Value—Enter a value for the ID.
-
Click
Add
to add this ID-Value pair to the ID-Value table.
To edit, replace, and delete ID-Value pairs:
-
Select the ID-Value pair from the ID-Value table.
-
Click
Edit
to edit the ID and Value fields. Edit the fields as required.
-
Click
Add
to add a new entry after you modify the fields.
-
Click
Replace
to replace the same entry with different values.
-
Click
Delete
to delete the entry from the ID-Value table.
|
|
Mandatory Fields
|
Check the check box to make this attribute a requirement in the User Properties page.
|
Add Policy Condition
|
Check the check box to create a custom condition from this attribute. When you check this option, you must enter a name in the Policy Condition Display Name field.
|
Policy Condition Display Name
|
Enter a name for the policy condition. After you submit this page, the condition appears in the
Policy Elements > Session Conditions > Custom
page.
|
Deleting an Internal User Identity Attribute
To delete an internal user identity attribute:
Step 1 Select
System Administration > Configuration > Dictionaries > Identity > Internal Users
.
The Attributes list for the internal user page appears.
Step 2 Check the check box of the attribute you want to delete.
Because deleting an identity attribute can take a long time to process, you can delete only one attribute at a time.
Step 3 Click
Delete
.
Step 4 For confirmation, click OK or Cancel.
The Attributes list for the internal user page appears without the deleted attribute.
Related Topics
Creating, Duplicating, and Editing an Internal Host Identity Attribute
To create, duplicate, and edit an internal host identity attribute:
Step 1 Select
System Administration > Configuration > Dictionaries > Identity > Internal Hosts
.
The Attributes list for the Internal Hosts page appears.
Step 2 Do one of the following:
-
Click
Create
.
-
Check the check box the attribute that you want to duplicate and click Duplicate.
-
Click the attribute name that you want to modify; or, check the check box for the name and click
Edit
.
The Identity Attribute Properties page appears.
Step 3 Modify the fields in the Identity Attributes Properties page as required. See
Table 18-13
for field descriptions.
Step 4 Click
Submit
.
The internal host attribute configuration is saved. The Attributes list for the Internal Hosts page appears with the new attribute configuration.
Related Topics
Deleting an Internal Host Identity Attribute
To delete an internal host identity attribute:
Step 1 Select
System Administration > Configuration > Dictionaries > Identity > Internal User
.
The Attributes list for the Internal Hosts page appears.
Step 2 Check the check box the attribute you want to delete.
Because deleting an attribute can take a long time to process, you can delete only one attribute at a time.
Step 3 Click
Delete
.
Step 4 For confirmation, click OK or Cancel.
The Attributes list for the Internal Hosts page appears without the deleted attribute.
Related Topics
Adding Static IP address to Users in Internal Identity Store
To add static IP address to a user in Internal Identity Store:
Step 1 Add a static IP attribute to internal user attribute dictionary:
Step 2 Select
System Administration > Configuration > Dictionaries > Identity > Internal Users.
Step 3 Click
Create.
Step 4 Add static IP attribute.
Step 5 Select
Users and Identity Stores > Internal Identity Stores > Users
.
Step 6 Click
Create.
Step 7 Edit the static IP attribute of the user.
Adding Local Server Certificates
You can add a local server certificate, also known as an ACS server certificate, to identify the ACS server to clients.
Step 1 Select
System Administration > Configuration > Local Server Certificates > Local Certificates
.
The Local Certificates page appears displaying the information in
Table 18-14
:
Table 18-14 Local Certificates Page
|
|
Friendly Name
|
Name that is associated with the certificate.
|
Issued To
|
Entity to which the certificate is issued. The name that appears is from the certificate subject.
|
Issued By
|
Trusted party that issued the certificate.
|
Valid From
|
Date the certificate is valid from.
|
Valid To (Expiration)
|
Date the certificate is valid to.
|
Protocol
|
Protocol associated with the certificate.
|
Step 2 Click
Add
.
Step 3 Enter the information in the Local Certificate Store Properties page as described in
Table 18-15
:
Importing Server Certificates and Associating Certificates to Protocols
The supported certificate formats are either DER or PEM.
Step 1 Select
System Administration > Configuration > Local Server Certificates > Local Certificates > Add
.
Step 2 Select
Import Server Certificate
>
Next
.
Step 3 Enter the information in the ACS Import Server Certificate as described in
Table 18-16
:
Table 18-16 Import Server Certificate Page
|
|
Certificate File
|
Select to browse the client machine for the local certificate file.
|
Private Key File
|
Select to browse to the location of the private key.
|
Private Key Password
|
Enter the private key password. The value may be minimum length = 0 and maximum length = 256.
|
|
EAP
|
Check to associate the certificate with EAP protocols that use SSL/TLS tunneling: EAP-TLS, EAP-FAST, and PEAP.
|
Management Interface
|
Check to associate the certificate with the management interface.
|
Allow Duplicate Certificates
|
Allows to add certificate with same CN and same SKI with different Valid From, Valid To, and Serial number.
|
|
Replace Certificate
|
Check to replace the content of an existing certificate with the one that you import, but retain the existing protocol selections.
|
Step 4 Click
Finish.
The new certificate is saved. The Local Certificate Store page appears with the new certificate.
Generating Self-Signed Certificates
Step 1 Select
System Administration > Configurations > Local Server Certificates > Local Certificates > Add.
Step 2 Select
Generate Self Signed Certificate
>
Next
.
Step 3 Enter the information in the ACS Import Server Certificate as described in
Table 18-17
:
Table 18-17 Generate Self Signed Certificate
|
|
|
Certificate subject entered during generation of this request. The Certificate Subject field may contain alphanumeric characters. The maximum number of characters is 1024. This field is prefixed with “cn=”.
|
Key Length
|
Key length entered during generation of this request.Values may be 512, 1024, 2048, or 4096. If you are deploying ACS as a FIPS-compliant policy management-engine, you must specify a 2048-bit or larger key length.
|
Digest to Sign with
|
Select either SHA1 or SHA256 as management certificates, from the dropdown list.
|
Expiration TTL
|
Select the maximum value in days, weeks, months, and years, and enter a positive integer.
|
|
EAP
|
Check to associate the certificate with EAP protocols that use SSL/TLS tunneling: EAP-TLS, EAP-FAST, and PEAP.
|
Management Interface
|
Check to associate the certificate with the management interface.
|
Allow Duplicate Certificates
|
Allows to add certificate with same CN and same SKI with different Valid From, Valid To, and Serial number.
|
|
Replace Certificate
|
Check to replace the content of an existing certificate with the one that you import, but retain the existing protocol selections.
|
Step 4 Click
Finish.
The new certificate is saved. The Local Certificate Store page appears with the new certificate.
Generating a Certificate Signing Request
Step 1 Select
System Administration > Configurations > Local Server Certificates > Local Certificates > Add.
Step 2 Select
Generate Certificate Signing Request
>
Next
.
Step 3 Enter the information in the ACS Import Server Certificate as described in
Table 18-18
:
Table 18-18 Generate Signing Requests
|
|
|
Certificate subject entered during generation of this request. The Certificate Subject field may contain alphanumeric characters. The maximum number of characters is 1024. This field is prefixed with “cn=”.
|
Key Length
|
Key length entered during generation of this request.Values may be 512, 1024, 2048, or 4096. If ACS is set to operate in FIPS mode, the certificate RSA key size must be 2048 bits or greater in size and use either SHA-1 or SHA-256 hash algorithm.
|
Digest to Sign with
|
Select either SHA1 or SHA256 as management certificates, from the dropdown list.
|
Step 4 Click
Finish.
The following message is displayed:
A server certificate signing request has been generated and can be viewed in the “Outstanding Signing Requests” list.
The new certificate is saved. The Local Certificate Store page appears with the new certificate.
Binding CA Signed Certificates
Use this page to bind a CA signed certificate to the request that was used to obtain the certificate from the CA.
Step 1 Select
System Administration > Configurations > Local Server Certificates > Local Certificates > Add.
Step 2 Select
Bind CA Signed Certificate
>
Next
.
Step 3 Enter the information in the ACS Import Server Certificate as described in
Table 18-19
:
Table 18-19 Bind CA Signed Certificate
|
|
Certificate File
|
Browse to the client machine and select the certificate file to be imported.
|
|
EAP
|
Check to associate the certificate with EAP protocols that use SSL/TLS tunneling: EAP-TLS, EAP-FAST, and PEAP.
|
Management Interface
|
Check to associate the certificate with the management interface.
|
Allow Duplicate Certificates
|
Allows to add certificate with same CN and same SKI with different Valid From, Valid To, and Serial number.
|
|
Replace Certificate
|
Check to replace the content of an existing certificate with the one that you import, but retain the existing protocol selections.
|
Step 4 Click
Finish.
The new certificate is saved. The Local Certificate Store page appears with the new certificate.
Related Topics
Editing and Renewing Certificates
You can renew an existing self-signed certificate without having to remove it and adding a new certificate. This ensures that any service that uses the local certificate continues without any interruption. To renew or extend a local server certificate:
1. Select
System Administration > Configuration > Local Server Certificates > Local Certificates
.
2. Click the name that you want to modify; or, check the check box for the Name, and click
Edit
.
3. Enter the certificate properties as described in
Table 18-20
:
Table 18-20 Edit Certificate Store Properties Page
|
|
|
Friendly Name
|
Name that is associated with the certificate.
|
|
Description of the certificate.
|
Issued To
|
Display only.
The entity to which the certificate is issued. The name that appears is from the certificate subject.
|
Issued By
|
Display only.
The certification authority that issued the certificate.
|
Valid From
|
Display only.
The start date of the certificate’s validity. An X509 certificate is valid only from the start date to the end date (inclusive).
|
Valid To (Expiration)
|
Display only.
The last date of the certificate’s validity.
|
Serial Number
|
Display only.
The serial number of the certificate.
|
|
EAP
|
Check for ACS to use the local certificate with EAP protocols that use SSL/TLS tunneling: EAP-TLS, EAP-FAST, and PEAP.
|
Management Interface
|
Check for ACS to use the local certificate for SSL client authentication.
|
Renew Self Signed Certificate
|
Certificate Expires On
|
Display only.
Date the certificate expires.
|
Renew Self Signed Certificate
|
Check to allow the renewal of a self signed certificate that expired.
|
Expiration TTL
|
Expiration TTL is the number of days, months, weeks, or years that you want to extend the existing certificate for. Valid options are: one day, one month, one week, and one year.
At a maximum, you can extend the certificate for a period of one year.
|
4. Click
Submit
to extend the existing certificate’s validity.
The Local Certificate Store page appears with the edited certificate.
Related Topic
Deleting Certificates
To delete a certificate:
Step 1 Select
System Administration > Configuration > Local Server Certificates > Local Certificates
.
Step 2 Check one or more check boxes of the certificates that you want to delete.
Step 3 Click
Delete
.
Step 4 For confirmation, click Yes or Cancel.
The Certificate Store page appears without the deleted certificate(s).
Related Topic
Exporting Certificates
To export a certificate:
Step 1 Select
System Administration > Configuration > Local Server Certificates > Local Certificates
.
Step 2 Check the check boxes of the certificates that you want to export, then click
Export
.
The Export Certificate dialog box appears.
Step 3 Select one of the following options:
-
Export Certificate Only
-
Export Certificate and Private Key
Step 4 Enter your private key password in the Private Key Password field.
Step 5 Enter the same password in the Confirm Password field.
Note Exporting the private key is not a secure operation and could lead to possible exposure of the private key.
Step 6 Click OK or Cancel.
Related Topic
Viewing Outstanding Signing Requests
Step 1 Select
System Administration > Configurations > Local Server Certificates > Outstanding Signing Request
.
The Certificate Signing Request page appears displaying the information described in
Table 18-21
:
Table 18-21 Certificate Signing Request Page
|
|
|
Name of the certificate.
|
Certificate Subject
|
Certificate subject entered during generation of this request. The Certificate Subject field may contain alphanumeric characters. The maximum number of characters is 1024. This field should automatically prefixed with “cn=”.
|
Key Length
|
Key length entered during generation of this request.Values may be 512, 1024, 2048, or 4096.
|
Timestamp
|
Date certificate was created.
|
Friendly Name
|
Name that is associated with the certificate.
|
Step 2 Click
Export
to export the local certificate to a client machine.
Configuring Local and Remote Log Storage
Log records are generated for:
-
Accounting messages
-
AAA audit and diagnostics messages
-
System diagnostics messages
-
Administrative and operational audit messages
The messages are arranged in tree hierarchy structure within the logging categories (see Configuring Logging Categories for more information).
You can store log messages locally or remotely, based on the logging categories and available disk spaces.
This section contains the following topics:
See Understanding Logging
for a description of the preconfigured global ACS logging categories and the messages that each contains.
Configuring Remote Log Targets
You can configure specific remote log targets (on a syslog server only) to receive the logging messages for a specific logging category. See Understanding Logging
for more information on remote log targets. See Configuring Logging Categories, for more information on the preconfigured ACS logging categories. ACS 5.8 allows you to send secure syslog messages to a remote log target. If you choose the secure syslog option, ACS logs the following messages in the System Diagnostic reports.
-
Remote syslog target is unavailable.
-
Remote syslog target connection is resumed.
-
Remote syslog target buffer is cleared.
To create a new remote log target:
Step 1 Choose
System Administration
>
Configuration
>
Log Configuration
>
Remote Log Targets
.
The Remote Log Targets page appears.
Step 2 Do one of the following:
-
Click
Create
.
-
Check the check box the remote log target that you want to duplicate and click
Duplicate
.
-
Click the name of the remote log target that you want to modify; or check the check box the name of the remote log target that you want to modify and click
Edit
.
-
One of these pages appears:
-
Remote Log Targets > Create, if you are creating a new remote log target.
-
Remote Log Targets > Duplicate: “
log_target”
, where
log-target
is the name of the remote log target you selected in Step 2, if you are duplicating a remote log target.
-
Remote Log Targets > Edit: “
log_target”
, where
log-target
is the name of the remote log target that you selected in Step 2, if you are modifying a remote log target.
Step 3 Complete the required fields as described in
Table 18-22
:
Table 18-22 Remote Log Targets Configuration Page
|
|
|
Name
|
Name of the remote log target. Maximum name length is 32 characters.
|
Description
|
Description of the remote log target. Maximum description length is 1024 characters.
|
Type
|
Type of remote log target—Syslog (the only option).
|
|
IP Address
|
IP address of the remote log target, in the format
x.x.x.x
.
|
Target Type
|
Select the type of syslog target type. By default it is set to UDP Syslog. The available target types are:
-
UDP Syslog—The log messages are sent to the remote syslog target over a UDP connection.
-
TCP Syslog—The log messages are sent to the remote syslog target over a TCP connection.
-
Secure TCP Syslog—The log messages are sent to the remote syslog target over a secure TCP connection. The administrator has to configure CA and server certificates in both ACS and the remote syslog target. ACS verifies the server certificates from the remote syslog server and if the certificates are valid, it establishes a secure TCP connection between ACS and the remote syslog target to send the log messages.
|
Use Advanced Syslog Options
|
Click to enable the advanced syslog options—port number, facility code, maximum length, buffer messages when server down, buffer size, reconnect timeout, select certificate authority, accept any syslog server. ACS displays the Advanced Syslog Options according to the selected target type.
|
Port
|
Port number of the remote log target used as the communication channel between the ACS and the remote log target.
-
The default port number for UDP Syslog is 514.
-
The default port number for TCP Syslog is 1468.
-
The default port number for Secure TCP Syslog is 6514.
|
Facility Code
|
Facility code. Valid options are:
-
LOCAL0 (Code = 16)
-
LOCAL1 (Code = 17)
-
LOCAL2 (Code = 18)
-
LOCAL3 (Code = 19)
-
LOCAL4 (Code = 20)
-
LOCAL5 (Code = 21)
-
LOCAL6 (Code = 22; default)
-
LOCAL7 (Code = 23)
|
Maximum Length
|
Maximum length of the remote log target messages. Valid options are from 200 to 8192. The default value is 1024.
|
Buffer Messages When Server Down
|
Check this check box if you want ACS to buffer the syslog messages when the TCP syslog targets and secure syslog targets are unavailable. ACS retries sending the messages to the target when the connection is re-established. After the connection is re-established, messages are sent in order from oldest to newest and buffered messages are always sent before new messages. If the buffer is full, old messages are discarded.
|
Buffer Size
|
(Required only when you check the Buffer Messages When Server Down check box.) Maximum size (in MB) of the buffer messages that can be stored in ACS when the remote syslog server is down. By default, it is set to 100 MB. The valid range is from 10 to 100 MB. Changing the buffer size clears the buffer and all existing buffered messages for the specific target are lost.
These buffer messages are cleared when you edit some of the options in the Remote Log Targets page. See the note below for more details.
|
Reconnect Timeout
|
(Applicable only for TCP Syslog and Secure TCP Syslog targets.)
The time interval at which ACS tries to reconnect to the remote syslog server when the remote syslog server is down and disconnected from ACS. The valid range is from 30 to 120 seconds. The default value is 30 seconds.
|
Select Certificate Authority
|
(Required only for Secure TCP Syslog targets.)
The administrator have to choose one of the installed CA certificates in the CTL to be used for Secure Syslog. ACS tries to find a first valid local certificate that was signed by the selected CA for TLS negotiation with the syslog server. The administrator cannot choose the specific certificate. If ACS cannot find a valid installed local certificate, it uses the management certificate.
|
Accept Any SysLog Server
|
(Applicable only for Secure TCP Syslog targets.)
Check this check box if you want ACS to ignore server certificate validation and accept any syslog server. By default, this option is unchecked. This option is disabled when you run ACS in FIPS mode.
Note You must uncheck this option if ACS is set to operate in FIPS mode.
|
Step 4 Click
Submit
.
The remote log target configuration is saved. The Remote Log Targets page appears with the new remote log target configuration.
Note • When you edit the IP Address, Target Type, Buffer Size, Maximum Length, or Port fields of a remote log target, ACS displays the following message in a pop up window:
Your changes will delete all not sent messages in buffer. Do you want to continue?
You can click OK to delete the buffer messages and save the changes made in the fields. Click Cancel if you do not want to delete the buffer messages.
-
When you use multiple remote log targets for an ACS instance and edit the IP Address, Target Type, Buffer Size, Maximum Length, or Port fields of a remote log target, the buffer messages specific only to the edited remote log target are deleted. This operation does not affect the buffer messages that are associated with the unedited other remote log targets.
-
When a remote log target of an ACS deployment goes down, ACS stores the log messages in the relevant instance’s buffer. For example, if the log message is created in the primary instance, ACS stores the messages in the primary instance’s buffer. If the log message is created in the secondary instances, ACS stores the messages in the corresponding secondary instance’s buffer.
-
In an ACS deployment, the server certificate issued by the remote log target’s CA should be installed in all ACS instances.
-
When you select Secure TCP as the target type for a remote log target, the log collector acts as both the syslog server and the client (internal communication is through SSL). In this case, the root CA that has issued the log collector’s management certificate must be installed in the CA trust list for the SSL handshake to be successful.
-
If the management certificate of the log collector has Key Usage (KU), Enhanced Key Usage (EKU), and Netscape certificate type fields, then both the server and client authentication details must be set in these fields where as the other ACS instances in the deployment must have only the client authentication details.
-
To send all CARS related log messages to the remote syslog server, execute the
logging
<
syslog ip
> command from ACS CLI. After executing this command, ACS does not send CARS related messages to the log collector server.
Related Topic
Deleting a Remote Log Target
To delete a remote log target:
Step 1 Select
System Administration
>
Configuration
>
Log Configuration
>
Remote Log Targets
.
The Remote Log Targets page appears, with a list of configured remote log targets.
Step 2 Check one or more check boxes the remote log targets you want to delete.
Step 3 Click
Delete
.
The following error message appears:
Are you sure you want to delete the selected item/items?
Step 4 Click
OK
.
The Remote Log Targets page appears without the deleted remote log targets.
Related Topic
Configuring the Local Log
Use the Local Configuration page to configure the maximum days to retain your local log data.
Step 1 Select
System Administration
>
Configuration
>
Log Configuration
>
Local Log Target
.
The Local Configuration page appears.
Step 2 In the Maximum log retention period box, enter the number of days for which you want to store local log message files, where
<num>
is the number of days you enter. Valid options are 1 to 365. (Default = 7.)
Note If you reduce the number of days for which to store the local log message files, the log message files older than the number of days you specify are deleted automatically.
You can click
Delete Logs Now
to delete the local logs, including all non-active log files, immediately. See Deleting Local Log Data for more information on deleting log data.
Step 3 Click
Submit
to save your changes.
Your configuration is saved and the Local Configuration page is refreshed.
Deleting Local Log Data
Use the Local Configuration page to manually delete your local log data. You can use this option to free up space when the local store is full. See Local Store Target for more information about the local store.
Step 1 Select
System Administration
>
Configuration
>
Log Configuration
>
Local Log Target
.
The Local Configuration page appears.
Step 2 Click
Delete Logs Now
to immediately delete all local log data files, except the log data in the currently active log data file.
The Local Configuration page is refreshed.
Configuring Logging Categories
This section contains the following topics:
All configuration performed for a parent logging category affects the children within the logging category. You can select a child of a parent logging category to configure it separately, and it does not affect the parent logging category or the other children.
Configuring Global Logging Categories
To view and configure global logging categories:
Step 1 Select
System Administration
>
Configuration
>
Log Configuration
>
Logging Categories
>
Global
.
The Logging Categories page appears; from here, you can view the logging categories.
Step 2 Click the name of the logging category you want to configure; or, click the radio button the name of the logging category you want to configure and click
Edit
.
Step 3 Complete the fields as described in
Table 18-23
.
Table 18-23 Global: General Page
|
|
|
Log Severity
|
For diagnostic logging categories, use the drop-down list box to select the severity level. (For audit and accounting categories, there is only one severity, NOTICE, which cannot be modified.) Valid options are:
-
FATAL—Emergency. ACS is not usable and you must take action immediately.
-
ERROR—Critical or error condition.
-
WARN—Normal, but significant condition. (Default)
-
INFO—Informational message.
-
DEBUG—Diagnostic bug message.
|
Configure Local Setting for Category
|
Log to Local Target
|
Check to enable logging to the local target.
For administrative and operational audit logging category types, logging to local target is enabled by default and cannot be disabled.
|
Local Target is Critical
|
Usable for accounting and for AAA audit (passed authentication) logging category types only
. Check the check box to make this local target the critical target.
For administrative and operational audit logging category types, the check box is checked by default and cannot be unchecked; the local target is the critical target.
|
Configure Logged Attributes
|
—
|
Display only
. All attributes are logged to the local target.
|
Skip Log Accounting Updates
|
Note This option is available from ACS 5.8 patch 7 or later.
Applicable only for Accounting (update packets)—Radius Accounting (interim–update) and TACACS accounting (watchdog) logging category type. When this option is enabled, accounting update packets are not sent to the log collector.
|
If you have completed your configuration, proceed to Step 6.
Step 4 To configure a remote syslog target, click the
Remote Syslog Target
and proceed to Step 5.
Step 5 Complete the Remote Syslog Target fields as described in
Table 18-24
:
Table 18-24 Global: Remote Syslog Target Page
|
|
|
Available targets
|
List of available targets. You can select a target from this list and move it to the Selected Targets list.
|
Selected targets
|
List of selected targets. You can select a target from this list and move it to the Available Targets list to remove it from your configuration.
|
Step 6 Click
Submit
.
The Logging Categories page appears, with your configured logging category.
Administrative and operational audit messages include audit messages of the following types:
-
Configuration changes
-
Internal user change password
-
Administrator access
-
Operational audit
Some of the operational audit messages are not logged in the local log target. See
Table 18-25
for a list of administrative and operational logs that are not logged in the local target. See Viewing ADE-OS Logs for information on how you can view these logs from the ACS CLI.
Table 18-25
lists a set of administrative and operational logs under various categories that are not logged to the local target.
Table 18-25 Administrative and Operational Logs Not Logged in the Local Target
|
|
Process-Management
|
-
ACS_START_PROCESS—ACS process started
-
ACS_STOP_PROCESS—ACS process stopped
-
ACS_START—All ACS processes started
-
ACS_STOP—All ACS processes stopped
-
WD_RESTART_PROCESS—ACS process restarted by watchdog
-
WD_CONFIG_CHANGE—Watchdog configuration reloaded
-
ACS_START_STOP_ERROR—ACS process reported start/stop error
|
DB-Management
|
-
CARS_BACKUP—CARS backup complete
-
CARS_RESTORE—CARS restore complete
-
ACS_BACKUP—ACS DB backup complete
-
ACS_RESTORE—ACS DB restore complete
-
ACS_SUPPORT—ACS support bundle collected
-
ACS_RESET—ACS DB reset
|
File-Management
|
-
ACS_DELETE_CORE—ACS core files deleted
-
ACS_DELETE_LOG—ACS log files deleted
|
Software-Management
|
-
ACS_UPGRADE—ACS upgraded
-
ACS_PATCH—ACS patch installed
-
UPGRADE_SCHEMA_CHANGE—ACS schema upgrade complete
-
UPGRADE_DICTIONARY—ACS dictionary upgrade complete
-
UPGRADE_DATA_MANIPULATION—ACS upgrade - data manipulation stage complete
-
UPGRADE_AAC—ACS AAC upgrade complete
-
UPGRADE_PKI—ACS PKI upgrade complete
-
UPGRADE_VIEW—ACS View upgrade complete
-
CLI_ACS_UPGRADE—ACS upgrade started
-
CLI_ACS_INSTALL—ACS install started
|
System-Management
|
-
ACS_MIGRATION_INTERFACE—ACS migration interface enabled/disabled
-
ACS_ADMIN_PSWD_RESET—ACS administrator password reset
-
CLI_CLOCK_SET—Clock set
-
CLI_TZ_SET—Time zone set
-
CLI_NTP_SET—NTP Server set
-
CLI_HOSTNAME_SET—Hostname set
-
CLI_IPADDRESS_SET—IP address set
-
CLI_IPADDRESS_STATE—IP address state
-
CLI_DEFAULT_GATEWAY—Default gateway set
-
CLI_NAME_SERVER—Name server set
-
ADEOS_XFER_LIBERROR—ADE OS Xfer library error
-
ADEOS_INSTALL_LIBERROR—ADE OS install library error
-
AD_JOIN_ERROR—AD agent failed to join AD domain
-
AD_JOIN_DOMAIN—AD agent joined AD domain
-
AD_LEAVE_DOMAIN—AD agent left AD domain
-
IMPORT_EXPORT_PROCESS_ABORTED—Import/Export process aborted
-
IMPORT_EXPORT_PROCESS_STARTED—Import/Export process started
-
IMPORT_EXPORT_PROCESS_COMPLETED—Import/Export process completed
-
IMPORT_EXPORT_PROCESS_ERROR—Error while Import/Export process
|
Related Topic
Viewing ADE-OS Logs
The logs listed in
Table 18-25
are written to the ADE-OS logs. From the ACS CLI, you can use the following command to view the ADE-OS logs:
show logging system ade/ADE.log
This command lists all the ADE-OS logs and your output would be similar to the following example.
Sep 29 23:24:15 cd-acs5-13-179 sshd(pam_unix)[20013]: 1 more authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.77.137.95 Sep 29 23:24:34 cd-acs5-13-179 sshd(pam_unix)[20017]: authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.77.137.95 user=ad Sep 29 23:24:36 cd-acs5-13-179 sshd[20017]: Failed password for admin from 10.77.137.95 port 3635 ssh2 Sep 30 00:47:44 cd-acs5-13-179 sshd(pam_unix)[20946]: authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.77.137.95 user=ad Sep 30 00:47:46 cd-acs5-13-179 sshd[20946]: Failed password for admin from 10.77.137.95 port 3953 ssh2 Sep 30 00:54:59 cd-acs5-13-179 sshd(pam_unix)[21028]: authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.77.137.95 user=ad Sep 30 00:55:01 cd-acs5-13-179 sshd[21028]: Failed password for admin from 10.77.137.95 port 3962 ssh2 Sep 30 00:55:35 cd-acs5-13-179 last message repeated 5 times Sep 30 00:55:39 cd-acs5-13-179 sshd[21028]: Accepted password for admin from 10.77.137.95 port 3962 ssh2 Sep 30 00:55:39 cd-acs5-13-179 sshd(pam_unix)[21038]: session opened for user admin by (uid=0) Sep 30 00:55:40 cd-acs5-13-179 debugd[2597]: hangup signal caught, configuration read Sep 30 00:55:40 cd-acs5-13-179 debugd[2597]: successfully loaded debug config Sep 30 00:55:40 cd-acs5-13-179 debugd[2597]: [21043]: utils: cars_shellcfg.c[118] [admin]: Invoked carsGetConsoleConfig Sep 30 00:55:40 cd-acs5-13-179 debugd[2597]: [21043]: utils: cars_shellcfg.c[135] [admin]: No Config file, returning defaults Sep 30 01:22:20 cd-acs5-13-179 sshd[21038]: Received disconnect from 10.77.137.95: 11: Connection discarded by broker Sep 30 01:22:20 cd-acs5-13-179 sshd(pam_unix)[21038]: session closed for user admin Sep 30 01:22:22 cd-acs5-13-179 debugd[2597]: hangup signal caught, configuration read Sep 30 01:22:22 cd-acs5-13-179 debugd[2597]: successfully loaded debug config Sep 30 02:48:54 cd-acs5-13-179 sshd[22500]: Accepted password for admin from 10.77.137.58 port 4527 ssh2 Sep 30 02:48:54 cd-acs5-13-179 sshd(pam_unix)[22504]: session opened for user admin by (uid=0) Sep 30 02:48:55 cd-acs5-13-179 debugd[2597]: hangup signal caught, configuration read Sep 30 02:48:55 cd-acs5-13-179 debugd[2597]: successfully loaded debug config
You can view the logs grouped by the module that they belong to. For example, the monitoring and troubleshooting logs contain the string
MSGCAT
and the debug logs contain the string
debug
.
From the ACS CLI, you can enter the following two commands to view the monitoring and troubleshooting logs and the administrative logs respectively:
-
show logging system | include MSGCAT
-
show logging system | include debug
The output of the
show logging system | include MSGCAT
would be similar to:
Sep 27 13:00:02 cd-acs5-13-103 MSGCAT58010/root: info:[ACS backup] ACS backup completed Sep 28 13:00:03 cd-acs5-13-103 MSGCAT58010/root: info:[ACS backup] ACS backup completed Sep 29 06:28:17 cd-acs5-13-103 MSGCAT58007: Killing Tomcat 8363 Sep 29 06:28:28 cd-acs5-13-103 MSGCAT58004/admin: ACS Stopped Sep 29 06:31:41 cd-acs5-13-103 MSGCAT58037/admin: Installing ACS Sep 29 09:52:35 cd-acs5-13-103 MSGCAT58007: Killing Tomcat 32729 Sep 29 09:52:46 cd-acs5-13-103 MSGCAT58004/admin: ACS Stopped Sep 29 09:53:29 cd-acs5-13-103 MSGCAT58004/admin: ACS Starting Sep 29 10:37:45 cd-acs5-13-103 MSGCAT58018/admin: [ACS-modify-migration-state] completed successfully - interface migration enable Sep 29 13:00:02 cd-acs5-13-103 MSGCAT58010/root: info:[ACS backup] ACS backup completed Sep 29 13:56:36 cd-acs5-13-103 MSGCAT58018/admin: [ACS-modify-migration-state] completed successfully - interface migration disable Sep 29 13:57:02 cd-acs5-13-103 MSGCAT58018/admin: [ACS-modify-migration-state] completed successfully - interface migration disable Sep 29 13:57:25 cd-acs5-13-103 MSGCAT58018/admin: [ACS-modify-migration-state] completed successfully - interface migration enable Sep 30 10:57:10 cd-acs5-13-103 MSGCAT58010/admin: info:[ACS backup] ACS backup completed
For more information on the
show logging
command, refer to
CLI Reference Guide for Cisco Secure Access Control System 5.8
.
Configuring Per-Instance Logging Categories
You can define a custom logging category configuration for specific, overridden ACS instances, or return all instances to the default global logging category configuration.
To view and configure per-instance logging categories:
Step 1 Select
System Administration
>
Configuration
>
Log Configuration
>
Logging Categories
>
Per-Instance
.
The Per-Instance page appears; from here, you can view the individual ACS instances of your deployment.
Step 2 Click the radio button associated with the name of the ACS instance you want to configure, and choose one of these options:
-
Click
Override
to override the current logging category configuration for selected ACS instances.
-
Click
Configure
to display the Logging Categories page associated with the ACS instance. You can then edit the logging categories for the ACS instance. See Displaying Logging Categories for field descriptions.
-
Click
Restore to Global
to restore selected ACS instances to the default global logging category configuration.
Your configuration is saved and the Per-Instance page is refreshed.
Related Topic
Configuring Per-Instance Security and Log Settings
You can configure the severity level and local log settings in a logging category configuration for a specific overridden or custom ACS instance. Use this page to:
-
View a tree of configured logging categories for a specific ACS instance.
-
Open a page to configure a logging category’s severity level, log target, and logged attributes for a specific ACS instance.
Step 1 Select
System Administration > Configuration > Log Configuration > Logging Categories > Per-Instance
, then click
Configure
.
The Per-Instance: Configuration page appears as described in Per-Instance: Configuration Page:
Table 18-26 Per-Instance: Configuration Page
|
|
Name
|
Expandable tree structure of AAA service logging categories.
|
Edit
|
Click to display a selected Logging Categories > Edit: “
lc_name
” page, where
lc_name
is the name of the logging category.
|
Step 2 Do one of the following:
-
Click the name of the logging category you want to configure.
-
Select the radio button associated with the name of the logging category you want to configure, and click
Edit
.
The Per-Instance: General page appears.
From here, you can configure the security level and local log settings in a logging category configuration for a specific ACS instance. See
Table 18-27
:
Table 18-27 Per-Instance: General Page
|
|
|
Log Severity
|
Use the list box to select the severity level for diagnostic logging categories. (For audit and accounting categories, there is only one severity, NOTICE, which cannot be modified.) Valid options are:
-
FATAL—Emergency. The ACS is not usable and you must take action immediately.
-
ERROR—Critical or error condition.
-
WARN—Normal, but significant condition. (Default)
-
INFO—Informational message.
-
DEBUG—Diagnostic bug message.
|
Configure Local Setting for Category
|
Log to Local Target
|
Check to enable logging to the local target.
For administrative and operational audit logging category types, logging to local target is enabled by default and cannot be disabled.
|
Local Target is Critical
|
Usable for accounting and for passed authentication logging category types only
. Check the check box to make this local target the critical target.
For administrative and operational audit logging category types, the check box is checked by default and cannot be unchecked; the local target is the critical target.
|
Configure Logged Attributes
|
—
|
Display only
. All attributes are logged to the local target.
|
Configuring Per-Instance Remote Syslog Targets
Use this page to configure remote syslog targets for logging categories.
Step 1 Select
System Administration > Configuration > Log Configuration > Logging Categories > Per-Instance
, then click
Configure
.
The Per-Instance: Configuration page appears as described in
Table 18-26
.
Step 2 Do one of the following actions:
-
Click the name of the logging category you want to configure.
-
Select the radio button associated with the name of the logging category you want to configure, and click
Edit
.
Step 3 Click the
Remote Syslog Target
tab.
The Per-Instance: Remote Syslog Targets page appears as described in
Table 18-28
:
Table 18-28 Per-Instance: Remote Syslog Targets Page
|
|
|
Available targets
|
List of available targets. You can select a target from this list and move it to the Selected Targets list.
|
Selected targets
|
List of selected targets. You can select a target from this list and move it to the Available Targets list to remove it from your configuration.
|
Displaying Logging Categories
You can view a tree of configured logging categories for a specific ACS instance. In addition, you can configure a logging category’s severity level, log target, and logged attributes for a specific ACS instance.
Step 1 Select
System Administration > Configuration > Log Configuration > Logging Categories > Per-Instance
, then click
Configure
.
Step 2 Complete the fields as described in
Table 18-29
:
Table 18-29 Per-Instance: Configuration Page
|
|
Name
|
Expandable tree structure of AAA services logging categories.
|
Edit
|
Click to display a selected Logging Categories > Edit: “
lc_name
” page, where
lc_name
is the name of the logging category.
|
Configuring the Log Collector
Use the Log Collector page to select a log data collector and suspend or resume log data transmission.
Step 1 Select
System Administration
>
Configuration
>
Log Configuration
>
Log Collector
.
The Log Collector page appears.
Step 2 Complete the Log Collector fields as described in
Table 18-30
:
Table 18-30 Log Collector Page
|
|
|
Current Log Collector
|
Display only.
Identifies the machine on which the local log messages are sent.
|
Select Log Collector
|
Use the drop-down list box to select the machine on which you want local log messages sent.
|
Set Log Collector
|
Click to configure the log collector according to the selection you make in the Select Log Collector option.
|
Step 3 Do one of the following:
-
Click
Suspend
to suspend the log data transmission to the configured log collector.
-
Click
Resume
to resume the log data transmission to the configured log collector.
Your configuration is saved and the Log Collector page is refreshed.
Viewing the Log Message Catalog
Use the Log Message Catalog page to view all possible log messages.
Choose
System Administration
>
Configuration
>
Log Configuration
>
Log Message Catalog
.
The Log Message Catalog page appears, with the fields described in
Table 18-31
, from which you can view all possible log messages that can appear in your log files.
Table 18-31 Log Messages Page
|
|
Message Code
|
Display only.
A unique message code identification number associated with a message.
|
Severity
|
Display only.
The severity level associated with a message.
|
Category
|
Display only.
The logging category to which a message belongs.
|
Message Class
|
Display only.
The group to which a message belongs.
|
Message Text
|
Display only.
English language message text (name of the message).
|
Description
|
Display only. English language text that describes the associated message.
|
Exporting Messages from the Log Message Catalog
ACS 5.8 provides the option to download syslog messages with message codes and description in the form of a CSV file. When you export the syslog messages, the filtering option does not work. ACS exports all syslog messages that are available in the Log Message Catalog page. The progress bar is not displayed during the export operation. If the export operation fails, ACS does not prompt to save the .csv file or the file can be empty.
Use the Log Message Catalog page to export log messages.
Step 1 Choose
System Administration
>
Configuration
>
Log Configuration
>
Log Message Catalog
.
The Log Message Catalog page appears, with the fields described in
Table 18-31
, from which you can view all possible log messages that can appear in your log files.
Step 2 Click Export.
ACS exports all syslog messages that are available in the Log Message Catalog page as a .csv file.
Step 3 Specify a location and click Save.
The .csv file is saved in the specified location.
Installing a License File
You can obtain a valid license file using the Product Activation Key (PAK) supplied with the product. To install a license file:
Step 1 Log into the ACS web interface.
The Initial Licenses page appears when you log in to the ACS machine for the first time.
Step 2 Click Cisco Secure ACS License Registration.
This link directs you to Cisco.com to purchase a valid license file from a Cisco representative.
Step 3 Click Install to install the license file that you purchased.
The ACS web interface log in page reappears. You can now work with the ACS application.
Related Topics
Viewing and Upgrading the Base Server License
ACS 5.8 allows you to upgrade or modify a base license without performing the reset config operation. To view and upgrade the base license:
Step 1 Select System Administration > Configuration > Licensing >
Bas
e Server License.
The Base Server License page appears with a description of the ACS deployment configuration and a list of the available deployment licenses. See Types of Licenses for a list of deployment licenses.
Table 18-33
describes the fields in the Base Server License page.
Table 18-33 Base Server License Page
|
|
ACS Deployment Configuration
|
Primary ACS Instance
|
Name of the primary instance created when you logged into the ACS 5.8 web interface.
|
Number of Instances
|
Current number of ACS instances (primary or secondary) in the ACS database.
|
Current Number of Configured IP Addresses in Network Devices
|
Total number of IP addresses in all the subnetworks that you have configured as part of network device configuration.
The number of devices is determined by the number of unique IP addresses that you configure. This includes the subnet masks that you configure. For example, a subnet mask of 255.255.255.0 implies 256 unique IP addresses and hence the number of devices is 256.
|
Maximum Number of IP Addresses in Network Devices
|
Maximum number of IP addresses that your license supports:
-
Base License—Supports 500 IP addresses.
The number of devices is determined by the number of unique IP addresses that you configure. This includes the subnet masks that you configure. For example, a subnet mask of 255.255.255.0 implies 256 unique IP addresses and hence the number of devices is 256.
-
Large Deployment—Supports an unlimited number of IP addresses.
|
Use this link to obtain a valid License File
|
Directs you to Cisco.com to generate a valid license file using the Product Activation Key (PAK)
|
Base License Configuration
|
ACS Instance
|
Name of the ACS instance, either primary or secondary.
|
Identifier
|
Name of the base license.
|
License Type
|
Specifies the base license type (permanent, evaluation).
|
Expiration
|
Specifies the expiration date for evaluation licenses. For permanent licenses, the expiration field indicates
permanent
.
|
Licensed to
|
Name of the company that this product is licensed to.
|
PAK
|
Name of the Product Activation Key (PAK) received from Cisco.
|
Version
|
Current version of the ACS software.
|
Step 2 Select the radio button the instance whose license you want to upgrade and click
Upgrade/Modify
.
The Base Server License Edit page appears.
The administrator can upgrade or modify a base license from ACS 5.8 web interface without resetting the configuration.
Step 3 Complete the fields as described in
Table 18-34
:
Table 18-34 Base Server License Edit Page
|
|
ACS Instance License Configuration
|
Version
|
Displays the current version of the ACS software.
|
ACS Instance
|
Displays the name of the ACS instance, either primary or secondary.
|
License Type
|
Specifies the license type.
|
Use this link to obtain a valid License File
|
Directs you to Cisco.com to purchase a valid license file from a Cisco representative.
|
|
License File
|
Click Browse to navigate to the directory that contains the license file and select it.
|
Step 4 Click
Submit
.
Related Topics
Available Downloads
This section contains information about the utilities and files that are available for download from the ACS web interface:
Downloading Migration Utility Files
To download migration application files and the migration guide for ACS 5.8:
Step 1 Choose System Administration > Downloads > Migration Utility.
The Migration from 4.x page appears.
Step 2 Click Migration application files, to download the application file you want to use to run the migration utility.
Step 3 Click Migration Guide, to download
Migration Guide for Cisco Secure Access Control System 5.8
.
Downloading UCP Web Service Files
You can download the WSDL file from this page to integrate ACS with your in-house portals and allow ACS users configured in the ACS internal identity store to change their own passwords. The UCP web service allows only the users to change their passwords. They can do so on the primary or secondary ACS servers.
The UCP web service compares the new password that you provide with the password policy that is configured in ACS for users. If the new password conforms to the defined criteria, your new password takes effect. After your password is changed on the primary ACS server, ACS replicates it to all the secondary ACS servers.
To download the UCP WSDL Files:
Step 1 Choose
System Administration > Downloads > User Change Password
.
The User Change Password (UCP) web service page appears.
Step 2 Click one of the following:
-
UCP WSDL
to download the WSDL file.
-
UCP Web application example to download the application file.
-
Python Script for Using the User Change Password Web Service
to download a sample Python script.
For more information on how to use the UCP web service, refer to
Software Developer’s Guide for Cisco Secure Access Control System
.
Downloading Sample Python Scripts
The Scripts page contains sample Python scripts for:
-
Using the UCP web service.
-
Automating the bulk import and export operations.
To download these sample scripts:
Step 1 Choose
System Administration > Downloads > Sample Python Scripts
.
The Sample Python Scripts page appears.
Step 2 Click one of the following:
-
Python Script for Using the User Change Password Web Service
—To download the sample script for the UCP web service.
-
Python Script for Performing CRUD Operations on ACS Objects
—To download the sample script for the import and export process.
Step 3 Save the script to your local hard drive.
The scripts come with installation instructions. For more information on how to use the scripts, refer to
Software Developer’s Guide for Cisco Secure Access Control System
.
Note The Cisco Technical Assistance Center (TAC) supports only the default Python Script. TAC does not offer any support for modified scripts.
Downloading Rest Services
ACS Rest Service allows to create, update, delete and retrieve objects from ACS Database.
Note You must enable the Rest Service using the command line for reading the WADL files.
To download ACS Rest Service WADL files:
Step 1 Choose
System Administration > Downloads > Rest Service
.
The Rest Service Page appears.
Step 2 Click one of the following:
-
Common or Identity
—To download XSD files that describe the structure of the objects supported on ACS 5.8 Rest interfaces.
-
Schema files
—To download the Schema files.
-
SDK Samples
—To download the SDK Samples.
Note After installing ACS 5.8 patch 4 or later, ACS uses TLSv1.2 as the default SSL context. The REST SDK uses SSL as the default context until ACS 5.8 patch 6. From ACS 5.8 patch 7, the REST SDK uses TLSv1.2 as the default SSL context with the condition that the REST client should be running JRE 1.7 or later. If you want the REST SDK to use TLSv1.0/SSL, you must check the Enable TLS 1.0 for https access check box in the Security Settings page and then modify the SSL Context parameter as TLSv1.0/SSL in the downloaded SDK sample regardless of the REST client's JRE version.
For more information on how to use the Rest Services, refer to
Software Developer’s Guide for Cisco Secure Access Control System
.