> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/support-application/sa-6/features/user-identity.md). # User Identity A Support Application 6 feature that displays the current logged-in user and their identity-provider connectivity status. ## Overview Use User Identity to view who is currently logged in on the device and their identity-provider (IdP) connectivity and login status. The feature also provides a paginated history of past logins. User Identity is available as an on-device tool within Support Application 6. It reads session state from the BlueFletch Launcher; it does not perform IdP authentication itself. ## User Guide ### Prerequisites * BlueFletch Launcher must be installed and running on the device. * The Launcher's ContentProvider must be reachable so that session state can be read. * The user must have completed login through the Launcher. ### Steps 1. Open the Support Application on the device. 2. Navigate to User Identity. 3. Review the current logged-in session, including user id, username, roles, and groups. 4. Check the IdP connectivity and login status for the current session. 5. Browse the paginated login history for past login records. #### Current Session Displays the current logged-in session, ie., user ID, username, roles, and groups, read from the BlueFletch Launcher. This enables the user to verify who is logged in and what roles and groups are assigned. #### Login History Displays paginated login history sourced from the local event-history store. This enables the user to review past login events without pulling data from a remote backend. #### Troubleshooting If you encounter the issue 'User Identity screen shows no user or stale user', check the following: 1. Verify that the BlueFletch Launcher is installed and running on the device. 2. Confirm that the Launcher's ContentProvider is reachable and returning session data. 3. Check whether the user has actually completed login through the Launcher (vs. Support Application launched standalone without a Launcher session). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/support-application/sa-6/features/user-identity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.