> 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/getting-started-with-passwordless-authentication.md).

# Getting started with passwordless authentication

This guide introduces passwordless authentication. You'll understand how authentication works, what you can protect with it, and the steps to go from a new tenant to a working passwordless login.

***

### What it is

1Kosmos replaces passwords with phishing-resistant, biometric authentication. Instead of a shared secret that can be stolen, reset, or phished, each sign-in is tied to a verified identity and backed by FIDO2 cryptographic keys. Users enroll their identity once and can then authenticate across systems, online or offline, without carrying a password or a separate hardware token for every app.

Because credentials are never stored or transmitted in a way an attacker can reuse, common attacks like phishing and credential stuffing are designed out rather than defended against. Teams typically also see fewer password-reset tickets, since recovery is handled through self-service biometric verification.

### How authentication works

Authentication happens in three stages:

1. **Verify identity with biometrics.** The user proves who they are with a biometric check that meets NIST IAL2/AAL2 assurance levels. Because the verified identity is stored in the cloud rather than bound to a single device, users can enroll once and authenticate from anywhere.
2. **Unlock cryptographic keys.** A successful biometric check unlocks the user's FIDO2 private key locally. No password or reusable credential is sent over the network, which is what makes the flow resistant to phishing.
3. **Authenticate across systems.** The same verified identity works across desktops, servers, web apps, SSO platforms, VPNs, and privileged systems, whether the device is online or offline.

### What you can secure

| Scenario                 | Description                                                                                                                                                                                 |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SSO & applications       | Authenticate once with biometrics and reach connected apps. Integrates with Microsoft, Okta, Ping, Saleforce, G-Suite, Entra EAM or Adaptive MFA can raise or lower friction based on risk. |
| Workstations             | Sign in to Windows, macOS, and Linux desktops, servers, and VDI with face or fingerprint, governed by centralized policy.                                                                   |
| Network & legacy systems | Extend passwordless to VPNs, network devices, and older applications over standard protocols, without rewriting them.                                                                       |
| Shared devices           | Workers authenticate at any shared terminal with a fingerprint after a one-time enrollment.                                                                                                 |
| Shared accounts          | Behavioral verification ties each action on a shared account back to an individual, producing a full audit trail.                                                                           |


---

# 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/getting-started-with-passwordless-authentication.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.