04-12-2023 07:39 AM
Hi,
the business doesn't want us to use the portal included in ISE for NAC bypass using MAC so wondering is there any other way of doing this i.e. using a script, or Service now integration etc.? or integration with sponsor portal?
Regards
Solved! Go to Solution.
04-13-2023 05:33 AM
API is probably your best/most scalable way to do this: https://developer.cisco.com/identity-services-engine/
If you are going to do this with the Sponsor Portal then you might as well just use the regular GUI.
04-12-2023 08:11 AM
To do what exactly? Bypass authentication? Is this wired or wireless? Guest? Something else? Do you mean you don't want to do MAB? Or rely on some other attribute for non-802.1X devices?
04-12-2023 08:20 AM
so users whose machine fail to authenticate using NAC (802.1x EAP-TLS), this bypass will provide them temporary access using MAC address.
04-12-2023 08:26 AM
So how would the MAC address get added to ISE? Is that what you are asking?
04-13-2023 01:19 AM
Exactly... I know how its done through ISE GUI but is it possible to either script it using API or integrate serviceNow or ISE sponsor portal etc.?
if so, do you have document that explains this part?
thanks
04-13-2023 05:33 AM
API is probably your best/most scalable way to do this: https://developer.cisco.com/identity-services-engine/
If you are going to do this with the Sponsor Portal then you might as well just use the regular GUI.
04-17-2023 02:35 AM
Hi,
thanks for your help so far. cant seem to find anyone with good scripting skill to utilise API. so came across BYOD portal.. and it ticks all the boxes however I can't seem to find a way to control access to the BYOD portal. Any ideas? can we somehow restrict this portal access to an AD group or perhaps a local ISE user group?
Regards
04-17-2023 05:38 AM
How is BYOD portal any different than just going to Context Visibility and manually placing the endpoint in the "bypass" group? Do you mean the My Devices portal?
04-17-2023 05:41 AM
Hi, yes I meant the device portal. apologies.
04-17-2023 06:14 AM
Again though, how is this different than just going to Context Visibility and placing the endpoint in the bypass group? Is the idea that this portal will be used by non-technical users? You can enable AD login to the My Devices portal but you have better RBAC through the regular admin GUI.
04-17-2023 06:26 AM
yh with devices portal you can capture more information plus the view is better. can you please share the steps on how to enable AD login to Devices porta? been looking from a while now but struggling.
Regards
04-17-2023 08:02 AM
Put your Active Directory Join Point here:
Administration -> Device Portal Management -> My Devices -> [select your portal] -> Portal Settings
04-18-2023 02:29 AM - edited 04-18-2023 02:53 AM
Hi Mate, thanks once again. wondering what would my policy look like, I have figured this part out. Just don;t know where to start with the policy. as AD Join Point, will allow the entire domain or the groups defined in that domain join point but I want to restrict access to a particular group.
appreciate all your help.
04-18-2023 04:46 AM
So if I am understanding your use-case correctly, you would have two Policy Sets. One for 802.1X and one for MAB. In your 802.1X policy you would use conditions to place different enforcement profiles based on AD Group (dACLS, VLANs, etc.). In your MAB policy you would have a condition for your My Devices Whitelist like "Endpoint ID group = [whatever your Endpoint ID group specified in the My Devices Portal]". Then a simple PermitAccess or whatever enforcement you like for this bypass list.
I would also suggest checking out the ISE YouTube content here: https://www.youtube.com/@CiscoISENetworkSecurity
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide