> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/authentication/orion-desktop-authenticator/overview.md). # Overview Orion Authenticator is a desktop application that delivers strong, passwordless authentication and TOTP-based MFA directly from a user's Mac or Windows workstation — without requiring a mobile device. *** ### When do I use Orion? Orion is especially beneficial for implementing MFA in environments where mobile devices are restricted. In such cases, users provide their password and a passcode from Orion as an extra layer of authentication. ### How it works Orion is installed as an agent on the user's workstation and launches a local HTTPS server on one of the ports in the range **47061–47069**. The local HTTPS server enables secure communication between Orion and the 1Kosmos AdminX login page in the browser. Orion supports two flows: * **Account onboarding** — Users enroll their account to Orion from the **Devices** tab in their AdminX profile. AdminX detects the installed authenticator on the workstation and forwards an enrollment request to Orion. * **MFA login** — When logging in to AdminX, users open Orion, generate a passcode using the **View your Passcode** option, and enter it on the login page along with their password. Orion also serves as a health agent, gathering information about the workstation's security posture to support adaptive authentication policies. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.1kosmos.com/authentication/orion-desktop-authenticator/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.