Active Directory Monitor Changelog: Difference between revisions
From Edge Threat Management Wiki - Arista
Jump to navigationJump to search
No edit summary |
|||
| (5 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
= 0.1.10.41 = | |||
* Properly parse Windows Server 2016 and beyond RADIUS event format. | |||
* Allow hostnames for ngfw servers instead of just IP addresses. | |||
* The Test operation for a ngfw server now checks that ADLM has event log access. | |||
= 0.1.10.40 = | |||
* Now RADIUS events are recognized and sent to the ngfw. | |||
* For Test, an attempt is made to distinguish the wget errors with more helpful messages (503=userapi not enabled, 403=userapi secret doesn't match). | |||
= 0.1.10.39 = | |||
* An error in the previous version prevented the notify service from properly working. This has been fixed. | |||
= 0.1.10.38 = | |||
* The Secret Key is now a required field. | |||
= 0.1.10.37 = | = 0.1.10.37 = | ||
* HTTPS connections to NGFW did not work with the 13.1 release. This has been fixed. | * HTTPS connections to NGFW did not work with the 13.1 release. This has been fixed. | ||
| Line 4: | Line 19: | ||
= 0.1.10.36 = | = 0.1.10.36 = | ||
* Removed ICC processing. If you need ICC handling, please [ | * Removed ICC processing. If you need ICC handling, please [https://downloads.untangle.com/public/UntangleActiveDirectoryMonitorSetupICC.exe Download] the previous version. | ||
= 0.1.10.35 = | = 0.1.10.35 = | ||
Latest revision as of 15:20, 27 November 2019
0.1.10.41
- Properly parse Windows Server 2016 and beyond RADIUS event format.
- Allow hostnames for ngfw servers instead of just IP addresses.
- The Test operation for a ngfw server now checks that ADLM has event log access.
0.1.10.40
- Now RADIUS events are recognized and sent to the ngfw.
- For Test, an attempt is made to distinguish the wget errors with more helpful messages (503=userapi not enabled, 403=userapi secret doesn't match).
0.1.10.39
- An error in the previous version prevented the notify service from properly working. This has been fixed.
0.1.10.38
- The Secret Key is now a required field.
0.1.10.37
- 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.
0.1.10.36
- Removed ICC processing. If you need ICC handling, please Download the previous version.
0.1.10.35
- In the notifier, handle unresponsive Next Generation Firewalls to avoid high loads.
0.1.10.34
- In the notifier, Exempt Usernames with spaces were not allowed.
0.1.10.33
- In the notifier, Next Generation Firewall Secret fields with the '+' character did not work.
0.1.10.32
- In the notifier, Next Generation Firewall appliance notifications caused a memory leak.
0.1.10.31
- In Settings, the minimum length of exempt user names was incorrectly restricted to six characters instead of of one.
0.1.10.29
- In the notifier, two or more exempt IP addresses would cause all notifications to stop.
0.1.10.28
- 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.
0.1.10.27
- 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.
0.1.10.26
- 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.
