please open a new discussion (i.e. post a question in the AAA forum) with your switch config and ISE screenshot. I'll be glad to check your setup and try to understand what is missing. This doc is meant to be basic config, so depending on the rest of your config, there might be a few traps.
Nicholas, you say that you attached the full switch config at the end of the document but I don't see it anywhere. Is it available for download? Thanks.
i did the same configuration and everything is ok except that the guest web browser is not automatically redirected to the portal and when i manually copy the url from the switch port it works as expected , how can i force the guest browser to be redirected automatically ?
Is it possible to return a dynamic VLAN (a restricted temporary VLAN) with the redirect address in the "mac not known" ?
With this method I am not able to distinguish between corporate user (AD auth) and Guest (internal). I might create a new authorization rule "is-a-CORPORATE" but in the 2nd AUTH (which define de VLAN) I can't make a difference between the 2. Any idea how to distinguish CORPORATE login from GUEST with CWA and apply a specific VLAN ?
Of course you can return a vlan with the mac-not-known. It should be a vlan with restricted access just for the guests logically.
You can, after the 3rd authorziation (the dynamic authorization, the CoA) return another vlan that will depend on the username typed in the guest portal. that's the magic of CWA.
Distinguishing between a corporate user and a guest ? Theoretically your switchport should be configured to do 802.1x first, which will give the employees the proper attributes. Then if the PC does not do dot1x of fail it, then you fallback to mab and this scenario.
If your employees are supposed to go through the guest portal as well to login, then it's on the 3rd authorization that you can return their attributes, because you learned their username
It is automatic. ISE might display to you "ip:port" in the configuration GUI, but in reality what will be sent is the PSN hostname of the ISE node against which the client authenticated (this is mandatory, only PSN where auth occured can do webauth for the client).
Therfore load balancing is achieved only by load balancing radius authentication. Portal will automatically be balanced as well then.
My challenge is that I cannot get public certificate for the domain.local as it is not a valid domain. And we do have domain.com but we do not have AD in domain.com. Since I would need to join ISE to domain so it will not accept the certificate with anything apart from its actual fqdn.And customer has this requirement that his guests must not get certificate warning so using public cert is must. I cannot use AD for LDAP as it does not support the MSCHAPV2 in LDAP. so I would need to put PKI infra then only this setup will work it seems there seems no option but Local PKI and use LDAP and then I can have ISE in domian.com withoout integrating it with AD.
just configure ISE cli with "ip domain name domain.com". As long as it's a valid DNS domain it's fine. it doesn't require to be an AD domain, there's no link between the 2 at all
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:
