> 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/prerequisites-and-requirements.md).

# Prerequisites and Requirements

Before installing Orion Authenticator, ensure the target workstation meets the requirements below

***

### Supported operating systems

{% tabs %}
{% tab title="macOS" %}

* **macOS 13** (Ventura) or later
* **350 MB** of available disk space
  {% endtab %}

{% tab title="Windows" %}

* **Windows 10**
* **Windows 11**
* **Windows Server 2016**
* **Windows Server 2019**
* **Windows Server 2022**
  {% endtab %}
  {% endtabs %}

### Network requirements

Orion runs a local HTTPS server to communicate securely with the 1Kosmos login page in the browser. One of the following ports must be available on the workstation:

| Port range  | Purpose                       |
| ----------- | ----------------------------- |
| 47061–47069 | Local HTTPS server (loopback) |

{% hint style="info" %}
These are loopback ports only — Orion does not open any inbound ports to the network. The HTTPS server is bound to `localhost`.
{% endhint %}

### Windows prerequisites

The following runtime libraries are required on Windows. The Orion installer attempts to download and install these automatically, but they can also be installed manually if your organization restricts installers from downloading third-party libraries.

| Runtime                              | Version      | Download (x86)                                          | Download (x64)                                          |
| ------------------------------------ | ------------ | ------------------------------------------------------- | ------------------------------------------------------- |
| Microsoft Visual C++ Redistributable | 2015–2022    | [x86](https://aka.ms/vs/17/release/vc_redist.x86.exe)   | [x64](https://aka.ms/vs/17/release/vc_redist.x64.exe)   |
| ASP.NET Core Runtime                 | 8.0 or later | [x86](https://dotnet.microsoft.com/download/dotnet/8.0) | [x64](https://dotnet.microsoft.com/download/dotnet/8.0) |
| .NET Desktop Runtime                 | 8.0 or later | [x86](https://dotnet.microsoft.com/download/dotnet/8.0) | [x64](https://dotnet.microsoft.com/download/dotnet/8.0) |

### Supported browsers

Orion supports account onboarding from the following browsers:

* Google Chrome
* Microsoft Edge
* Mozilla Firefox
* Safari (macOS only)
* Brave

{% hint style="warning" %}
**Brave users** — Disable **Shields** when onboarding accounts. Brave's privacy protections block certain cross-origin requests required for the browser to detect Orion on the workstation.
{% endhint %}

### Permissions

Orion requires the following permissions to function:

* **Local HTTPS certificate trust** — Orion installs a certificate into the workstation's trust store to enable secure communication between the local HTTPS server and the browser
* **File system access** — Read and write to the installation directory for log files and account data
* **Network access** — Outbound HTTPS to the 1Kosmos platform


---

# 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/prerequisites-and-requirements.md?ask=<question>&goal=<user_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.