mirror of
https://github.com/Unleash/unleash.git
synced 2024-11-01 19:07:38 +01:00
b2b19e4970
## About the changes Refactor the main nav, with the following goals: * Communicate the value of each section vs the format (ex: “Understanding Unleash” vs “Topic Guides”) * Make space for the Feature Flag tutorials section that we’re starting to build * Scope updates to navigation and pages that need updates based on new URLs & organization * Update URLs to follow the new hierarchy without breaking links (adding redirects & editing internal links between pages as needed) ### Important files sidebar.js docusaurus.config.js ## Discussion points * Redirects can't be tested out of prod, which is a bummer :/ * Some URLs have been preserved untouched while we monitor for potential negative SEO impact of client-side redirects * It's a large PR (sorry). Nav changes and file movements impacted lots of files. --------- Co-authored-by: Thomas Heartman <thomas@getunleash.ai>
43 lines
1.6 KiB
Markdown
43 lines
1.6 KiB
Markdown
---
|
|
title: Login History
|
|
---
|
|
|
|
:::info Availability
|
|
|
|
Login history is an enterprise feature available from Unleash 4.22 onwards.
|
|
|
|
:::
|
|
|
|
Unleash's login history lets you track login events in your Unleash instance, and whether the attempts were successful in logging in or not.
|
|
|
|
|
|
|
|
For each login event, it lists:
|
|
|
|
- **Created**: When it happened
|
|
- **Username**: The username that was used
|
|
- **Authentication**: The authentication type that was used
|
|
- **IP address**: The IP address that made the attempt
|
|
- **Success**: Whether the attempt was successful or not
|
|
- **Failure reason**: If the attempt was not successful, the reason why
|
|
|
|
You can see the failure reason by hovering over the "False" badge in the "Success" column.
|
|
|
|
|
|
|
|
Use the login history to:
|
|
|
|
- Audit login events in your Unleash instance
|
|
- Identify failed login attempts and investigate the cause
|
|
- Debug misconfigured authentication providers
|
|
|
|
The login history is mutable: You can remove individual login events or clear the entire history by deleting all of them.
|
|
|
|
Finally, the login history can be downloaded ([how do I download my Unleash login history](../how-to/how-to-download-login-history.mdx)) for external backups, audits, and the like.
|
|
|
|
## Retention
|
|
|
|
Events in the login history are retained for 336 hours (14 days).
|
|
|
|
Events older than the retention period are automatically deleted, and you won't be able to recover them. If you would like to collect login event information past the retention period, we suggest periodically downloading the login history.
|