> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/platform-administration/maintenance-mode-applications/snapper/configure-snapper-authentication.md).

# Configure Snapper authentication

Configure authentication for Snapper.

Configure Snapper authentication so users can sign in with Microsoft 365 credentials and use Microsoft Entra ID-backed access control.

{% hint style="warning" %}
Snapper, Inflight Wallboard, and WebWallboard use the same authentication method per UCC service. If authentication is enabled for one application, it is also enabled for the other applications using that service. WebWallboard configuration is handled by Dialogue Cloud, but Snapper and Inflight Wallboard client applications must each be configured for this authentication method.
{% endhint %}

## Before you begin

You need:

* A Microsoft Entra ID app registration for authentication.
* The authentication URL for the customer realm:

  ```
  https://login.anywhere365.cloud/auth/realms/<GUID>
  ```
* The redirect URI configured on the Microsoft Entra ID app registration:

  ```
  https://login.anywhere365.cloud/auth/realms/<GUID>/broker/oidc/endpoint
  ```

For customers migrating from the previous backend platform, the legacy hostname can appear as:

```
https://auth.anywhere365.cloud/auth/realms/<GUID>
```

Use `login.anywhere365.cloud` for current DC2024.01f-or-later activation and new setup.

## Enable authentication in Snapper

1. Open Snapper.
2. Go to **Settings**.
3. Select **General**.
4. In **Security**, enter the authentication URL.

   ```
   https://login.anywhere365.cloud/auth/realms/<GUID>
   ```
5. Confirm that the URL is populated before changing **Access Control**.
6. Turn **Access Control** on.
7. Optional: turn **Access Control Browser** on when a Windows Conditional Access policy blocks the built-in mini browser.
8. Confirm that intended users exist in Microsoft Entra ID.

<figure><img src="https://2358142509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJymOXTAFZLWXmwvtHWu8%2Fuploads%2Fgit-blob-3f31628c12aeec4b1ec00d3b2753e0dfec82fe58%2Fsnapper-settings-security-modern-view.png?alt=media" alt="Snapper security settings in modern view"><figcaption></figcaption></figure>

<figure><img src="https://2358142509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJymOXTAFZLWXmwvtHWu8%2Fuploads%2Fgit-blob-60b6c52531e12efbe94416d2ba1a32c7bf338467%2Fsnapper-enable-authentication.png?alt=media" alt="Snapper Access Control setting enabled for authentication"><figcaption></figcaption></figure>

{% hint style="warning" %}
Enter the authentication URL before turning on Access Control. If Access Control is switched on while the URL is empty, Snapper attempts a sign-in that it cannot validate. If this happens, turn off Access Control manually in the local Snapper `config.xml` file.
{% endhint %}

## Unattended installation parameters

For unattended installation, use:

| Parameter                              | Value                                                                   |
| -------------------------------------- | ----------------------------------------------------------------------- |
| `FEATURETOGGLEACCESSCONTROL`           | `true`                                                                  |
| `FEATURETOGGLEACCESSCONTROLURL`        | `https://login.anywhere365.cloud/auth/realms/<GUID>`                    |
| `FEATURETOGGLEACCESSCONTROLWEBBROWSER` | `true` when the default Windows desktop browser must be used for login. |

## Verify authentication

1. Restart Snapper.
2. Start Snapper as a test user.
3. Confirm that Snapper opens the expected sign-in experience.
4. Confirm that the user can complete sign-in and connect to the expected UCC.


---

# 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://atlas.anywhere.now/platform-administration/maintenance-mode-applications/snapper/configure-snapper-authentication.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.