Get Principal MFA Audit Log
DescriptionRetrieves all the audits for the MFA de/activation, enable/disable, login, login using recovery code and recovery code generation/deletion. The events received are sorted by date in descending order ie the most recent ones will appear first. Note: startDate and endDate format is epoch time in milliseconds.
Principal user is identified via a token. The token should be passed in a header called csp-auth-token.
Access Policy
| Role | User Accounts | Service Accounts (Client Credentials Applications) |
|---|---|---|
| All Roles | ✔️ | ❌ |
Request
URLURL
Request Body
{
"endDate": 0,
"startDate": 0
}
Start Date
End Date
The device names
The event ids
The maximum results per page
The index that the set of results will begin with
Actions
Possible values are: MFA_ACTIVATION, MFA_DEACTIVATION, MFA_ENABLE, MFA_DISABLE, MFA_DEVICE_NAME_UPDATE, MFA_AUTHENTICATION_SUCCESS, MFA_AUTHENTICATION_FAILURE, MFA_RECOVERY_CODE_AUTHENTICATION_SUCCESS, MFA_RECOVERY_CODE_AUTHENTICATION_FAILURE, MFA_RECOVERY_CODES_GENERATION, AUTHENTICATION_WITHOUT_MFA
Authentication
Response
Response BodyResponse Body
200 OK
{
"itemsPerPage": 25,
"startIndex": 5,
"totalResults": 2000
}
Number of items per page.
Start index of the results.
Total number of results if available
Errors
End date must be greater than start date OR Start date cannot be of future OR Date should be given as epoch OR Specified action is not supported OR Cannot exceed the limit of 20 event ids OR Cannot exceed the limit of 20 device names ORCombination of page and size exceeds max limit of records fetch
Unauthenticated User
The user is forbidden to use the API
No user with given token exists
The request could not be processed due to a conflict
The user has sent too many requests
An unexpected error has occurred while processing the request
