> 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/how-to-articles/configure-domain-single-sign-on-sso.md).

# Configure domain single sign-on (SSO)

Enable domain single sign-on in Devolutions Server by configuring Windows Authentication in IIS and Server Manager, then activating SSO settings.

{% hint style="info" %}
The machine hosting Devolutions Server must be joined to the [configured domain](/server/web-interface/administration/configuration/server-settings/general/authentication/domain.md) for domain single sign-on (SSO) to work.
{% endhint %}

These steps provide the information to enable the ***domain single sign-on (SSO)*** feature in Devolutions Server.

### Steps

1. Open the ***Server Manager*** desktop application and go to ***Manage – Add Roles and Features***.
2. In the ***Server Roles*** section, ensure that the ***Windows Authentication*** server role is installed.
3. When done, you can close the ***Add Roles and Features Wizard*** and ***Server Manager*** windows.
4. Open the ***IIS Manager***. Select the server in the tree view and open the ***Feature Delegation*** in the ***Management*** section.
5. Set the ***Authentication - Windows*** feature to the ***Read/Write*** value.
6. When done, you can close the ***IIS Manager***.
7. In ***Administration – Server Settings – Authentication*** of the Devolutions Server instance web interface, check the ***Enable domain single sign-on (SSO)*** option box. When done, click on the ***Save*** button.
8. Set the administrator credential properties in the ***Administration – Server Settings – Authentication – Domains***.
9. Finally, in the workspace configuration of each client in Remote Desktop Manager, enable the ***Use Windows authentication*** option, then click ***OK*** when done to save your modifications.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/server/knowledge-base/how-to-articles/configure-domain-single-sign-on-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 `build a script that syncs our docs to a CMS` 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.