12-17-2018 07:23 AM
Good day,
Is there any official support for integrating ISE with fortigate/FortiAPs?
Want to know the possibility of using ISE as the RADIUS server to authenticate wireless users using fortiAPs.
Solved! Go to Solution.
12-17-2018 07:29 AM
It depends on how you want them to integrate with ISE. ISE is a standards-based RADIUS server. Chances are good that basic 802.1X authentication will work. However, if you are looking to integrate for use cases such as BYOD then you will most likely have to figure out if they support RADIUS CoA and URL-Redirect. You can also explore using a NAD profile.
Regards,
-Tim
12-17-2018 07:29 AM
It depends on how you want them to integrate with ISE. ISE is a standards-based RADIUS server. Chances are good that basic 802.1X authentication will work. However, if you are looking to integrate for use cases such as BYOD then you will most likely have to figure out if they support RADIUS CoA and URL-Redirect. You can also explore using a NAD profile.
Regards,
-Tim
12-17-2018 07:49 AM
Oh ok thanks alot for the reply.
That's some good information
Do you know if there are any official documentation to refer to customers that are interested in doing this type of integration.
12-17-2018 08:01 AM
12-17-2018 10:23 AM
Ok cool thanks alot.
Will check the links.
12-17-2018 10:03 AM
12-17-2018 10:24 AM
Got you,
thanks much for the reply.
02-17-2019 11:18 PM
did you ever get this to work?
12-24-2019 08:25 AM
I am also curious if you ever got this to work and what dictionary set you used?
04-16-2020 09:56 AM
Hi guys,
Unfortunately i was unable to configure/test out this kind of implementation. Has anyone been able to?
08-11-2020 08:13 PM
After working with TAC and fortinet support I was able to get this to work for 802.1x authentications.
11-26-2020 02:46 PM
Hi AdamF1,I wish you are very well.
Could you share the configuration that was done so that everything works correctly.
I thank you
11-30-2020 06:31 AM
Create a new device profile for Fortinet controller and apply the appropriate protocols and conditions to 802.1x and MAB.
-MAB- IEEE 802.11 and call check
-802.1x- IEEE 802.11
Build out the controller in network devices and apply the profile.
Depending on your policies you may need to build out a new one that sits above it as authentication may continue to try and use it and fail. You can make it unique by setting it to something like call-station id ( mac address of controller), this way only devices utilizing it will hit the policy. Just be careful when editing your global policy sets and conditions you create as you could impact your current authentications.
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