Note: Due to NETBIOS limitations, ACS hostnames must contain less than or equal to 15 characters. Issue the hostname command in order to configure HOSTNAME on the ACS as shown here: hostname acs51 >HEADER command in order to configure DOMAIN-NAME on the ACS as shown here: ip domain-name
Issue the nslookup command in order to verify the domain name reachability as shown.
#HTTPS SECURE ACCESS ACS MEMBER LOGIN WINDOWS#
Note: The DNS IP address is provided by your Windows domain administrator. The output of show clock command is shown here: acs51/admin# show clockĬonfigure DNS on ACS with the command in config mode as shown here: ip name-server 192.168.26.55
Now verify the Timezone, Date and Time with the show clock command. To verify that ACS processes are running, use the You must restart ACS.ĭo you want to restart ACS now? (yes/no) yes An example is shown here: clock set Jun 8 10:36:00 2012Ĭlock was modified. In order to configure date and time manually use the clock set command in exec mode. Refer to ACS 5.x: Cisco ACS Synchronization with NTP Server Configuration Example for more information on NTP configuration. If this action resulted in a clock modification, you must restart ACS. NTP server can be configured with the ntp server command in config mode as shown. These are the steps to configure NTP server: If you do not have NTP server, then skip to step 4. In case your AD domain controller is synchronized with an NTP server that resides in your network, it is highly recommended to use the same NTP server on the ACS. You can find your specific timezone by exec mode show timezones command. Note: Asia/Kolkata is the timezone used in this document. Issue the clock timezone command in config mode as shown in order to configure the TIMEZONE on the ACS in order to match with that on the domain controller. SSH to the ACS appliance and enter the CLI credentials. Complete these steps in order to configure ACS 5.x Application Deployment Engine (ADE-OS): Also, define the DNS server on the ACS in order to be able to resolve the domain name from the ACS 5.x. The integration of ACS 5.x with AD allows the use of the existing AD users, machines and their group mapping.ĪCS 5.x integrated with AD provides these features:Ĭertificate Retrieval for EAP-TLS AuthenticationĬonfiguration Configure ACS 5.x Application Deployment Engine (ADE-OS)īefore you integrate ACS 5.x to the AD, ensure that the TimeZone, Date & Time on the ACS matches with that on the AD primary domain controller. Windows Active Directory provides many features that are used in the daily network usage. Refer to the Cisco Technical Tips Conventions for more information on document conventions. If your network is live, make sure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment.
#HTTPS SECURE ACCESS ACS MEMBER LOGIN SOFTWARE#
The information in this document is based on these software and hardware versions: Note: Integration of Microsoft Windows Server 2008 R2 Domain with ACS is supported from ACS 5.2 and later. Use Microsoft Windows Server 2003 Domain, Microsoft Windows Server 2008 Domain or Microsoft Windows Server 2008 R2 Domain as these are supported by ACS 5.x. Windows Active Directory Domain to be used needs to be fully configured and operational.
Prerequisites RequirementsĮnsure that you meet these requirements before you attempt this configuration: ACS authenticates these resources against AD.
ACS uses Microsoft Active Directory (AD) as an external identity store to store resources such as users, machines, groups, and attributes. This document provides a sample configuration to integrate Microsoft Active Directory with Cisco Secure Access Control System (ACS) 5.x and later.
0 kommentar(er)
