> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/es/troubleshooting/access-token-issues/failed-to-obtain-access-token.md).

# No se pudo obtener el token de acceso

## Problema

Cuando intentas iniciar sesión en KONNEKT, aparece el mensaje de error "No se pudo obtener el token de acceso".

## Causa

KONNEKT no admite tener "Excluded Apps" en una directiva de Conditional Access de Microsoft Entra ID que requiera MFA en combinación con una sesión de Windows sin SSO.

## Solución alternativa

Nuestra solución alternativa recomendada es habilitar la máquina Windows para que conserve un Primary Refresh Token (PRT), por ejemplo, haciendo que el dispositivo esté unido a Microsoft Entra o registrado en Microsoft Entra. Consulte [aquí ](https://learn.microsoft.com/en-us/entra/identity/devices/concept-primary-refresh-token#how-is-a-prt-issued)para más detalles.

Otras alternativas son (no se recomiendan realmente):

* Quite el requisito de MFA de la directiva de Conditional Access correspondiente. Para mantener cierta seguridad en las directivas de CA sin MFA, podría imponer [Ubicaciones de confianza (p. ej., direcciones IP públicas de sus hosts VDI)](https://learn.microsoft.com/en-us/entra/identity/conditional-access/location-condition)

o

* utilice una directiva de Conditional Access sin "Excluded Apps". Consulte también [configuración de Conditional Access](/es/installation/security/conditional-access.md).

## Solución

Se implementó una solución en la versión 2.10 de KONNEKT - "[OAuth mejorado](/es/configuration/system-settings/enhanced-authentication.md)".


---

# 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.konnekt.io/es/troubleshooting/access-token-issues/failed-to-obtain-access-token.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.