| Summary: | ASTERISK-22578: Invalid manager logins aren't reported via security events: Invalid IE Specified ERROR | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | |
| Date Opened: | 2013-09-23 13:21:20 | Date Closed: | 2013-10-03 14:29:03 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/ManagerInterface |
| Versions: | 12.0.0-alpha1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | # Attempt to login via some AMI account
# Specify an invalid secret # The security event framework spits out the following errors: {noformat} *CLI> [Sep 23 13:18:58] WARNING[8623]: security_events.c:551 add_json_object: Required IE '43' for security event type '12' not present [Sep 23 13:18:58] ERROR[8623]: security_events.c:766 ast_security_event_report: Failed to issue security event of type InvalidPassword. {noformat} There's a programming error in that there code. | ||
| Comments: | By: Kinsey Moore (kmoore) 2013-10-03 14:01:56.051-0500 Digging through diffs and change logs, it looks like this was caused by r337595 setting the new IEs for chan_sip's usage of the existing invalid password event as required IEs instead of optional IEs since AMI authentication obviously works a bit differently than SIP authentication. | ||