> 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/powershell-universal/security.md).

# 🔒Security

- [About](https://docs.devolutions.net/powershell-universal/security/security.md): Configure authentication and role-based authorization in PowerShell Universal, covering claim mapping, policy scripts, and app tokens.
- [Local Accounts](https://docs.devolutions.net/powershell-universal/security/local-accounts.md): Create and manage local accounts in PowerShell Universal, configure the default administrator account, and enforce password restrictions.
- [Forms Authentication](https://docs.devolutions.net/powershell-universal/security/forms-authentication.md): Customize the forms authentication script in PowerShell Universal to validate credentials, set claims, and support Basic authentication and Windows login.
- [Authorization](https://docs.devolutions.net/powershell-universal/security/authorization.md): Configure role-based authorization in PowerShell Universal using claim mapping, policy scripts, and built-in roles to control platform access.
- [App Tokens](https://docs.devolutions.net/powershell-universal/security/app-tokens.md): Grant, manage, and migrate PowerShell Universal app tokens for API access, covering roles, signing keys, and enhanced token security.
- [Enterprise Security](https://docs.devolutions.net/powershell-universal/security/enterprise-security.md): Explore enterprise security features in PowerShell Universal, including multiple authentication schemes and fine-grained Admin Console permissions.
- [Client Certificate](https://docs.devolutions.net/powershell-universal/security/enterprise-security/client-certificate.md): Enable client certificate authentication in PowerShell Universal and use roles.ps1 to evaluate certificate claims for authorization decisions.
- [OpenID Connect](https://docs.devolutions.net/powershell-universal/security/enterprise-security/openid-connect.md): Configure OpenID Connect authentication in PowerShell Universal with Entra ID or Okta, including claim mapping and delegated access tokens.
- [SAML2](https://docs.devolutions.net/powershell-universal/security/enterprise-security/saml2.md): Configure SAML2 authentication in PowerShell Universal with identity providers like Entra ID, Okta, and Shibboleth, including metadata and claim mapping.
- [WS-Federation](https://docs.devolutions.net/powershell-universal/security/enterprise-security/ws-federation.md): Configure WS-Federation authentication in PowerShell Universal with ADFS or Azure Active Directory, including relying party trust setup.
- [Windows SSO](https://docs.devolutions.net/powershell-universal/security/enterprise-security/windows-sso.md): Enable Windows single sign-on authentication in PowerShell Universal using Kerberos or NTLM, covering IIS and non-IIS hosting configurations.
- [Permissions](https://docs.devolutions.net/powershell-universal/security/enterprise-security/permissions.md): Manage fine-grained permissions in PowerShell Universal to control access to resources by identity or role using scoped permission identifiers.


---

# 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.devolutions.net/powershell-universal/security.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.