Guest

Cisco Identity Services Engine

Central Web Authentication on the WLC and ISE Configuration Example

Techzone Article content

Document ID: 115732

Updated: Jan 02, 2014

Contributed by Nicolas Darchis, Cisco TAC Engineer.

   Print

Introduction

This document describes the multiple methods to complete central web authentication on the Wireless LAN Controller (WLC).

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco Identity Services Engine Software Release 1.2
  • Cisco WLC Software Release 7.3.102.0

Configure

The first method is local web authentication. In this case, the WLC redirects the HTTP traffic to an internal or external server where the user is prompted to authenticate. The WLC then fetches the credentials (sent back via an HTTP GET request in the case of an external server) and makes a RADIUS authentication. In the case of a guest user, an external server (such as Identity Services Engine (ISE) or NAC Guest Server (NGS)) is required because the portal provides features such as device registering and self-provisioning. The flow includes these steps:

  1. The user associates to the web authentication Service Set Identifier (SSID).

  2. The user opens the browser.

  3. The WLC redirects to the guest portal (such as ISE or NGS) as soon as a URL is entered.
  4. The user authenticates on the portal.

  5. The guest portal redirects back to the WLC with the credentials entered.

  6. The WLC authenticates the guest user via RADIUS.

  7. The WLC redirects back to the original URL.

This flow includes several redirections. The new approach is to use central web authentication. This method works with ISE (versions later than 1.1) and WLC (versions later than 7.2). The flow includes these steps:

  1. The user associates to the web authentication SSID, which is in fact open+macfiltering and no layer 3 security.

  2. The user opens the browser.

  3. The WLC redirects to the guest portal.

  4. The user authenticates on the portal.

  5. The ISE sends a RADIUS Change of Authorization (CoA - UDP Port 1700) to indicate to the controller that the user is valid, and eventually pushes RADIUS attributes such as the Access Control List (ACL).

  6. The user is prompted to retry the original URL.

The setup used is:

WLC Configuration

The WLC configuration is fairly straightforward. A trick is used (same as on switches) in order to obtain the dynamic authentication URL from the ISE (since it uses Change of Authorization (CoA), a session must be created and the session ID is part of the URL). The SSID is configured in order to use MAC filtering. The ISE is configured in order to return an access-accept even if the MAC address is not found, so that it sends the redirection URL for all users. 

In addition to this, RADIUS Network Admission Control (NAC) and Authentication, Authorization, and Accounting (AAA) Override must be enabled. The RADIUS NAC allows the ISE to send a CoA request that indicates that the user is now authenticated and is able to access the network. It is also used for posture assessment, in which case the ISE changes the user profile based on the posture result.

Ensure that the RADIUS server has RFC3576 (CoA) enabled, which is by default.

The final step is to create a redirect ACL. This ACL is referenced in the access-accept of the ISE and defines what traffic should be redirected (denied by the ACL) and what traffic should not be redirected (permitted by the ACL). Here you just prevent from redirection traffic towards the ISE. You might want to be more specific and only prevent traffic to/from the ISE on port 8443 (guest portal), but still redirect if a user tries to access the ISE on port 80/443.

central-web-auth-07.png

Configuration is now complete on the WLC.

ISE Configuration

Create the Authorization Profile

On the ISE, the authorization profile must be created. Then, the authentication and authorization policies are configured. The WLC should already be configured as a network device.

In the authorization profile, enter the name of the ACL created earlier on the WLC.

  1. Click Policy, and then click Policy Elements.

  2. Click Results.

  3. Expand Authorization, and then click Authorization profile.

  4. Click the Add button in order to create a new authorization profile for central webauth.

  5. In the Name field, enter a name for the profile. This example uses WLC_CWA.

  6. Choose ACCESS_ACCEPT from the Access Type drop-down list.

  7. Check the Web Redirection check box, and choose Centralized Web Auth from the drop-down list.

  8. In the ACL field, enter the name of the ACL on the switch that defines the traffic to be redirected. This examples uses cwa_redirect.

  9. Choose Default from the Redirect drop-down list. (Choose something other than default if you use a custom portal other than the default.)

Create an Authentication Rule

Ensure that the ISE accepts all of the MAC authentications from the WLC and make sure it will pursue authentication even if the user is not found.

Under the Policy menu, click Authentication.

The next image shows an example of how to configure the authentication policy rule. In this example, a rule is configured that triggers when MAB is detected.

  • Enter a name for your authentication rule. This example uses MAB, which already exists by default on ISE Version 1.2.

  • Select the plus (+) icon in the If condition field.

  • Choose Compound condition, and then choose Wired_MAB OR Wireless_MAB.

  • Click the arrow located next to and ... in order to expand the rule further.

  • Click the + icon in the Identity Source field, and choose Internal endpoints.

  • Choose Continue from the If user not found drop-down list.

Create an Authorization Policy

Configure the authorization policy. One important point to understand is that there are two authentications/authorizations:

  • The first is when the user associates to the SSID and when the central web authentication profile is returned (unknown MAC address, so you must set the user for redirection).
  • The second is when the user authenticates on the web portal. This one matches the default rule (internal users) in this configuration (it can be configured in order to meet your requirements). It is important that the authorization part does not match the central web authentication profile again. Otherwise, there will be a redirection loop. The Network Access:UseCase Equals Guest Flow attribute can be used in order to match this second authentication. The result looks like this:

Complete these steps in order to create the authorization rules as shown in the previous images:

  1. Create a new rule, and enter a name. This example uses Guest Redirection.

  2. Click the plus (+) icon in the condition field, and choose to create a new condition.

  3. Expand the Expression drop-down list.

  4. Choose Network Access, and expand it.

  5. Click AuthenticationStatus, and choose the Equals operator.

  6. Choose UnknownUser in the right-hand field.

  7. On the General Authorization page, choose WLC_CWA (Authorization Profile) in the field to the right of the word then.

    This step allows the ISE to continue even though the user (or the MAC address) is not known.

    Unknown users are now presented with the Login page. However, once they enter their credentials, that is an authentication that succeeds if the client credentials are valid despite what you configured in the authentication/authorization policy. As of ISE Versions 1.1 and 1.2, portal authentications do not follow the authentication/authorization rules and succeed if valid. Thus, there is no need to create a rule that permits access upon successful portal login.

  8. Click the Actions button located at the end of the Guest Redirection rule, and choose to insert a new rule before it.

    Note: It is very important that this new rule comes before the Guest Redirection rule.



  9. Enter a name for the new rule. This example uses Guest Portal Auth.

  10. In the condition field, click the plus (+) icon, and choose to create a new condition.

  11. Choose Network Access, and click UseCase.

  12. Choose Equals as the operator.

  13. Choose GuestFlow as the right operand.

  14. On the authorization page, click the plus (+) icon (located next to then) in order to choose a result for your rule.

    You can choose a Permit Access option or create a custom profile in order to return the VLAN or attributes that you like. Note that on top of If GuestFlow, you can add more conditions in order to return various authz profiles based on the user group. As mentioned in Step 7, this Guest Portal Auth rule matches upon the second MAC address authentication initiated after the successful portal login and after ISE sent a CoA in order to reauthenticate the client. The difference with this second authentication is that, instead of coming to ISE with simply its MAC address, ISE remembers the username given in the portal. You can make this authorization rule take into accout the credentials entered a few milliseconds before in the guest portal.

Enable the IP Renewal (Optional)

If you assign a VLAN, the final step is for the client PC to renew its IP address. This step is achieved by the guest portal for Windows clients. If you did not set a VLAN for the 2nd AUTH rule earlier, you can skip this step.

If you assigned a VLAN, complete these steps in order to enable IP renewal:

  1. Click Administration, and then click Guest Management.

  2. Click Settings.

  3. Expand Guest, and then expand Multi-Portal Configuration.

  4. Click DefaultGuestPortal or the name of a custom portal you created.

  5. Click the VLAN DHCP Release check box.

    Note: This option works only for Windows clients.

Anchor-Foreign Scenario

This setup can also work with the auto-anchor feature of the WLCs. The only catch is that since this web authentication method is Layer 2, you have to be aware that it will be the foreign WLC that does all of the RADIUS work. Only the foreign WLC contacts the ISE, and the redirection ACL must be present also on the foreign WLC.

Just like in other scenarios, the foreign WLC quickly shows the client to be in the RUN state, which is not entirely true. It simply means that traffic is sent to the anchor from there. The real client state can be seen on the anchor where it should display CENTRAL_WEBAUTH_REQD.

Note: The anchor-foreign setup with CWA only works in Release 7.3 or later.

Verify

Once the user is associated to the SSID, the authorization is displayed in the ISE page.

The client details in the WLC show that the redirection URL and ACL are applied.

Now when any address is opened on the client, the browser is redirected to the ISE. Ensure that the Domain Name System (DNS) is set up correctly.

Network access is granted after the user accepts the policies.

As shown in the example ISE, the authentication, change of authorization, and profile applied is permitAccess.

The previous screenshot is taken from ISE Version 1.1.x where each single authentication step shows clearly.

The next screenshot is taken from ISE Version 1.2 where ISE summarizes several authentications performed by the same client in one line. Although more practical in real life, the Version 1.1.x screenshot shows more clearly what exactly happens for the sake of clarity in this example.

On the controller, the Policy Manager state and RADIUS NAC state changes from POSTURE_REQD to RUN.

Note: In Release 7.3 or later, the state is not called POSTURE_REQD anymore, but is now called CENTRAL_WEBAUTH_REQD.

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.

Updated: Jan 02, 2014
Document ID: 115732