Confirmed users
491
edits
Services/KeyExchange: Difference between revisions
Jump to navigation
Jump to search
→CEF Logging
| Line 365: | Line 365: | ||
* Bad action taken against a valid channel id (denoted by 400 error code) | * Bad action taken against a valid channel id (denoted by 400 error code) | ||
** Examples: non-existent x-keyexchange-id, bad x-keyexchange-id | ** Examples: non-existent x-keyexchange-id, bad x-keyexchange-id | ||
* | * Action taken against an invalid channel id (400 errors only, not 404 errors) | ||
** Examples: request for invalid channel id with or without x-keyexchange-id | ** Examples: request for invalid channel id with or without x-keyexchange-id | ||
* IP address sent to black list due to DOS prevention controls | * IP address sent to black list due to DOS prevention controls | ||
| Line 372: | Line 372: | ||
** Examples: Client unable to complete j-pake sync for any number of reasons and falls back to original sync approach | ** Examples: Client unable to complete j-pake sync for any number of reasons and falls back to original sync approach | ||
** Reported by client to server via reporting API | ** Reported by client to server via reporting API | ||
====Application Logging==== | ====Application Logging==== | ||
* Full application logging will be created to enable incident response review | * Full application logging will be created to enable incident response review | ||