cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
725
Views
0
Helpful
4
Replies

ISE 2.3 - CWA Redirect

Nayan.Patel85
Beginner
Beginner

Hi,

 

We are deploying ISE 2.3.

We use CWA for multi-factor authentication for Wireless and Wired employees.

 

1st issues) When a user goes from Wired connection to Wireless connection, CWA redirection does not work as expected, I can see he is getting correct authorization profile with correct redirect URL and redirect ACL, and it launches the browser automatically, but never able to make it to CWA portal.

User has to reboot the PC.

 

2nd) If user's PC goes to sleep while he was connected to wireless and if wakes up his pc redirect does not work at that time as well.

 

We are using the same CWA portal for Wireless and Wired.

 

Thanks

 

1 Accepted Solution

Accepted Solutions

Jason Kunst
Cisco Employee
Cisco Employee
This seems like the PC might be confused on having multiple interfaces in redirect state? If both nics are on at same time and connected then the OS might route differently depending on conditions. Have you tried controlling your NICs? For example if there is a problem disable the other NIC to make sure the OS is not routing funny?

Some customers on windows have been forced to control their NICs with Anyconnect NAM (network access manager) which won’t allow the wireless NIC to be up when connected on wired

Why do they need wired and wireless running at same time? What’s wrong with always wireless or always wired?

View solution in original post

4 Replies 4

gbekmezi-DD
Contributor
Contributor
Does the client browser not redirect, or is the redirect url not rendering?

Jason Kunst
Cisco Employee
Cisco Employee
This seems like the PC might be confused on having multiple interfaces in redirect state? If both nics are on at same time and connected then the OS might route differently depending on conditions. Have you tried controlling your NICs? For example if there is a problem disable the other NIC to make sure the OS is not routing funny?

Some customers on windows have been forced to control their NICs with Anyconnect NAM (network access manager) which won’t allow the wireless NIC to be up when connected on wired

Why do they need wired and wireless running at same time? What’s wrong with always wireless or always wired?

Jason,

Thanks for your response.
We don’t need both wireless and wired active at the same time.
We are running into issues when wired user disconnects from wired connection and switch to wireless.
Then user is not being redirected to CWA portal.
I believe it has to do with Machine Authentication. User was previously machine authenticated using wired NIC and now if he switches to wireless machine authentication will not happen unless he reboots or logs out-logs in.

Ok you’re mixing machine auth with CWA then? And dealing with supplicant issues now. Right the machine won’t send machine auth if switching networks while user is logged in due to Microsoft supplicant not supporting it. If you’re doing that then why are you doing CWA on top of it? Why not do eap chaining perhaps with anyconnect? Things are a lot smoother
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers