Does the latest version of ISE forward Radius Accounting information to remote destinations? Or does it still just send out in syslog format?
Customer is attempting RSSO with Fortinet Firewall and ISE 1.4 is performing Radius functions. Radius user attributes are not being passed to Fortinet. So Fortinet is reporting usage info by ip address not user identity.
No, ISE does not currently support the forwarding of RADIUS Accounting if not acting as a RADIUS Proxy. As noted, it is possible to set optional log targets for RADIUS Accounting logs, but these are not native RADIUS packets.
No, ISE does not currently support the forwarding of RADIUS Accounting if not acting as a RADIUS Proxy. As noted, it is possible to set optional log targets for RADIUS Accounting logs, but these are not native RADIUS packets.
Sorry for resurrecting this from the dead. I understand this is currently not supported in ISE but is there any roadmap for this feature? Some Firewalls like SonicWall still don't support syslog for the IP-Username mapping so they require Radius Acct.
Please reach out to our Product managers (internal email ise-pm@cisco.com<mailto:ise-pm@cisco.com>) to ask for a feature request
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:
