> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/user-guides/es/tips-and-tricks/using-windows-hello-or-touch-id-with-sso.md).

# Usar Windows Hello o Touch ID con SSO

Iniciar sesión con Windows Hello en una bóveda vinculada a SSO.

Keeper admite iniciar sesión con Windows Hello o Touch ID en una bóveda vinculada a un proveedor SSO como Microsoft Azure. Para configurarlo, siga las instrucciones siguientes.

(1) Inicie sesión en su bóveda con su SSO como de costumbre y haga clic en el **menú desplegable de la cuenta (su correo) > Configuración** **> Seguridad**.

(2) Active Windows Hello (o Touch ID si está en un Mac). Tenga en cuenta que si ya había intentado usar este ajuste, debe desactivarlo y volver a activarlo para restablecer el almacenamiento de la contraseña maestra en su dispositivo.

(3) La próxima vez que inicie sesión en la aplicación de escritorio de Keeper, haga clic en el botón "Windows Hello" o "Touch ID".

(4) Podrá iniciar sesión en su bóveda con Windows Hello o Touch ID, sin tener que iniciar sesión constantemente con su proveedor SSO.

{% hint style="warning" %}
Si recibe un error al intentar iniciar sesión con Windows Hello o Touch ID, desactive el ajuste y vuelva a activarlo.
{% 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.keeper.io/user-guides/es/tips-and-tricks/using-windows-hello-or-touch-id-with-sso.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.