> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/frequently-asked-questions/how-to-resolve-error-500-on-user-authentication.md).

# How to resolve Error 500 on user authentication

## Problem

In some cases, when you try to authenticate a user, an exception is shown: 

{% code overflow="wrap" %}

```json
{
    "Type": "Exception",
    "Title": "An error occurred.",
    "Status": 500,
    "Detail": "An error was encountered while handling the remote login."
    "Instance": "/signin-oidc",
    "Extensions": {}
}
```

{% endcode %}

## Solution

1. Log in to the Microsoft Azure portal at <https://portal.azure.com>.
2. Open the portal menu and select **Microsoft Entra ID**.
3. On the left pane, select **App registrations**.
4. Click **All applications.**
5. Click the application you created for Parallels DaaS.
6. Select **Authentication** in the left blade.
7. Select **ID tokens** **(used for implicit and hybrid flows)**.
8. Click **Save**.

<figure><img src="/files/DzG4WiHGQuyuVbaL1Ype" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/frequently-asked-questions/how-to-resolve-error-500-on-user-authentication.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.