> 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/windows-workstation-mfa/authentication-methods.md).

# Authentication Methods

The Windows Workstation MFA Agent supports multiple authentication methods. The method presented to a user at login is determined by the Adaptive Auth Journey configured for them in AdminX.

***

### Available Authentication Methods

| Method                        | Requires Mobile App | Works Offline        | Minimum Version |
| ----------------------------- | ------------------- | -------------------- | --------------- |
| Password + OTP                | ✅ (for OTP)         | ✅ (Account OTP only) | All versions    |
| Push Notification             | ✅                   | ❌                    | All versions    |
| QR Code                       | ✅                   | ❌                    | All versions    |
| FIDO / 1Key                   | ❌                   | ❌                    | All versions    |
| SMS / Email / Voice OTP       | ❌                   | ❌                    | v2.0.6.0+       |
| Behavior Authentication + PIN | ❌                   | ✅ (cached PIN)       | v2.1.2.0+       |
| Run As / UAC Elevation        | Depends on method   | ✅                    | All versions    |

{% hint style="info" %}
**Note:** The methods available to a user at login depend entirely on the Adaptive Auth Journey configured for them in AdminX. A method listed here will not appear at login unless it is configured in a journey.
{% endhint %}


---

# 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/windows-workstation-mfa/authentication-methods.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.