Active Directory Monitor Changelog
From Edge Threat Management Wiki - AristaJump to navigationJump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
- The Secret Key is now a required field.
- HTTPS connections to NGFW did not work with the 13.1 release. This has been fixed.
- Settings now has a test button that attempts to log into the selected ngfw server as "admtest" and return an error if it is unable to complete the notification.
- Removed ICC processing. If you need ICC handling, please Download the previous version.
- In the notifier, handle unresponsive Next Generation Firewalls to avoid high loads.
- In the notifier, Exempt Usernames with spaces were not allowed.
- In the notifier, Next Generation Firewall Secret fields with the '+' character did not work.
- In the notifier, Next Generation Firewall appliance notifications caused a memory leak.
- In Settings, the minimum length of exempt user names was incorrectly restricted to six characters instead of of one.
- In the notifier, two or more exempt IP addresses would cause all notifications to stop.
- In Settings, a new Apply button will save settings and restart the notifier but not exit the Settings application.
- The Notifier did not send the configured domain to the ICC appliance.
- Notifier memory usage was too high.
- In a new install environment, some defaults were not properly set.
- In Settings, the Help button now launches help.
- In Settings, after saving, all IP addresses are now resorted.
- IP ranges are now supported for IP exemptions.
- In Settings, when selecting an ICC or Next Generation Firewall IP address, the text was nearly the same color as the select background.
- The number of exempt IP addresses has been expanded from 20 to 100.
- The number of appliance IP addresses has been expanded from 10 to 20 each.