Login History
Login History shows every sign-in to your Tenant, including failed attempts and lockouts. It is available to Tenant Admins: in the Admin app, select Users, then Login History.
Use it to see who has signed in and when, to spot repeated failed attempts, and to find out why someone cannot sign in.
What each entry shows
| Column | What it shows |
|---|---|
| When (UTC) | When the attempt happened, in UTC (Coordinated Universal Time) |
| User Name | The user who signed in or was refused |
| Method | How the user signed in: Microsoft, Password, ApiToken (a program using an API token) or TokenLogin (a user signing in with an API token on the token login page) |
| Outcome | Succeeded, Failed, RefusedLocked (refused because the user or token was locked out) or LockedOut (this attempt started a lockout) |
| Reason | Why an attempt failed or was refused |
| IP Address | The address the attempt reached Magic Suite from |
| Reported Client IP | The user's own address, as passed on by the Magic Suite app they were using. It is reported by the app and not checked, so treat it as a guide |
| Locked Until (UTC) | On a lockout, when the lockout ends |
| API Token | The ID of the API token used, where there was one |
| User Agent | The browser or program that made the attempt |
On smaller screens the last four columns are hidden. Use Search to find entries by user name, reason or IP address.
Passwords and API token keys are never recorded. An attempt with a user name that matches no one is not shown, because it may contain a mistyped password.
Note: programs that use an API token, such as scheduled reports and the Magic Suite Agent, sign in on every job, so their successful sign-ins are not listed. Their failed attempts are.
Lockout
After a number of failed sign-ins in a row, a user is locked out for a period. While they are locked out:
- Every sign-in is refused, even with the right details
- Their existing sessions stop working
- Their API tokens are refused too
A successful sign-in resets the count, and failures older than the lockout period no longer count towards one. The lockout ends by itself when the period is over. Super Admins choose the number of failed attempts and the length of the lockout, and can turn lockout off.
Repeated failed attempts with an API token lock that token out only from the IP address they came from, so that someone else cannot lock your own programs out.
How long it is kept
Login History is kept for as long as the Audit Logs.