> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/knowledge-base/troubleshooting-articles/credentials-prompt-instead-of-domain-single-sign-on.md).

# Credentials prompt instead of domain single sign-on

Fixes the Windows credentials prompt shown instead of silent domain single sign-on when signing in to Devolutions Server from Remote Desktop Manager.

After Devolutions Server is updated, signing in to a Devolutions Server workspace from Remote Desktop Manager with domain single sign-on (SSO) is no longer silent. A Windows credentials prompt asks for the domain username and password. After the credentials are entered, the sign-in continues with multifactor authentication (MFA) when it is enabled, or with the [device sign-in confirmation page](https://docs.devolutions.net/server/knowledge-base/troubleshooting-articles/device-sign-in-confirmation-when-signing-in-to-devolutions-server.md) when it is not.

The prompt appears with every version of Remote Desktop Manager. Depending on the version and the authentication browser mode, Remote Desktop Manager shows the Devolutions Server sign-in page in its embedded login window or in the default browser. Installing the same version of Remote Desktop Manager on every computer does not remove the prompt.

## Why the prompt is displayed

Recent versions of Devolutions Server include a security fix for the phishing attack described in the [DEVO-2026-0035 security advisory](https://devolutions.net/security/advisories/DEVO-2026-0035/). Before the fix, Remote Desktop Manager could complete a domain SSO sign-in in the background, without showing any page to the user. An attacker could use this behavior to approve a sign-in on their own device without any action from the user.

Since the fix, Devolutions Server accepts Windows authentication only on its sign-in page. Remote Desktop Manager therefore opens the sign-in page, and the page starts the domain SSO sign-in itself. Remote Desktop Manager has no setting that restores the background sign-in.

The sign-in page runs in a browser: the embedded login window of Remote Desktop Manager on Windows uses Microsoft Edge WebView2, and the default browser is often Microsoft Edge or Google Chrome. These browsers send the Windows credentials of the signed-in user automatically only to sites in the Local intranet zone of Windows. A Devolutions Server URL with a fully qualified name, such as `https://dvls.example.com`, is not detected as an intranet site. Windows treats it as an Internet zone site, so the browser shows a credentials prompt instead of signing in silently.

## Confirm the cause

1. On an affected computer, open the Devolutions Server web interface URL in Microsoft Edge.
2. Under ***Choose your authentication method***, select ***Domain single sign-on (SSO)***.

If Microsoft Edge also displays a credentials prompt, the Devolutions Server URL is not in the Local intranet zone on that computer.

{% hint style="info" %}
The ***Domain single sign-on (SSO)*** option is displayed only when ***Enable domain single sign-on (SSO)*** is selected in ***Administration*** – ***Server settings*** – ***Authentication***. To configure domain SSO, see [Configure domain single sign-on (SSO)](https://docs.devolutions.net/server/knowledge-base/how-to-articles/configure-domain-single-sign-on-sso.md).
{% endhint %}

{% hint style="warning" %}
Some organizations configure a Microsoft Edge policy that lets Microsoft Edge send Windows credentials to specific servers. On those computers, Microsoft Edge can sign in silently while Remote Desktop Manager still displays the prompt. A silent sign-in in Microsoft Edge does not rule out the zone as the cause.
{% endhint %}

## Solution

Add the Devolutions Server URL to the Local intranet zone on the client computers. The following procedure uses a Group Policy Object (GPO) to apply the setting to every computer of the domain.

1. On a computer with the Group Policy Management Console, open the GPO that applies to the client computers.
2. Go to ***Computer Configuration*** – ***Administrative Templates*** – ***Windows Components*** – ***Internet Explorer*** – ***Internet Control Panel*** – ***Security Page***.
3. Open ***Site to Zone Assignment List***.
4. Select ***Enabled***.
5. Select ***Show***.
6. In ***Value name***, enter the Devolutions Server URL, such as `https://dvls.example.com`.
7. In ***Value***, enter `1`.
8. Select ***OK*** to close the list.
9. Select ***OK*** to save the policy.
10. On each client computer, run `gpupdate /force` in a command prompt, or wait for the next Group Policy refresh.
11. Restart Remote Desktop Manager.

{% hint style="info" %}
The same policy also exists under ***User Configuration***. The value `1` assigns the site to the Local intranet zone. The other values are `2` for Trusted sites, `3` for Internet, and `4` for Restricted sites.
{% endhint %}

Automatic sign-in also depends on the ***User Authentication – Logon*** setting of the Local intranet zone. Its default value, ***Automatic logon only in Intranet zone***, sends the Windows credentials automatically. If a policy changes this setting, the prompt can remain after the URL is added to the zone.

## What to expect after the change

The credentials prompt is no longer displayed. Remote Desktop Manager still opens the Devolutions Server sign-in page, then:

* With MFA enabled: The user completes the MFA step, and the sign-in completes.
* Without MFA: The [device sign-in confirmation page](https://docs.devolutions.net/server/knowledge-base/troubleshooting-articles/device-sign-in-confirmation-when-signing-in-to-devolutions-server.md) is displayed. Select ***Yes, it’s me*** to complete the sign-in. This confirmation is part of the security fix and cannot be turned off.

The sign-in page is displayed only when Remote Desktop Manager has to sign in again. When Remote Desktop Manager can restore its existing session with Devolutions Server, it does not open the sign-in page.

On macOS and Linux, Remote Desktop Manager does not use the Windows security zones, so this solution does not apply.

## If the prompt persists

If the prompt is still displayed after the Devolutions Server URL is added to the Local intranet zone, create a Remote Desktop Manager debug log of a sign-in that shows the prompt:

1. In Remote Desktop Manager, go to ***File*** – ***Settings*** – ***Advanced***.
2. In the ***Settings*** tab, select the browse button next to ***Debug level***.
3. Select ***Debug*** and ***API***.
4. Select ***Save***.
5. Restart Remote Desktop Manager.
6. Sign in to the Devolutions Server workspace until the prompt is displayed.
7. Copy the RemoteDesktopManager.debug file from the configuration folder.
8. Clear the debug level categories, then restart Remote Desktop Manager.

Send the following information to [Devolutions support](https://devolutions.net/support/):

* The RemoteDesktopManager.debug file.
* The DPS\_Main log files from the App\_Data folder of the Devolutions Server website, from every Devolutions Server node. The lines in these files do not identify the node.
* Whether several Devolutions Server nodes answer on the Devolutions Server URL, and whether they all run the same version.
* The exact time and the username of a sign-in that shows the prompt.
* A screenshot of the prompt.

For more information on the debug log, see [Debugging](https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/debugging). To choose between the embedded login window and the default browser, see [Set the authentication browser mode](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/set-the-authentication-browser-mode).


---

# 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.devolutions.net/server/knowledge-base/troubleshooting-articles/credentials-prompt-instead-of-domain-single-sign-on.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.
