> 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/wallboard/configure-wallboard-authentication.md).

# Configure Wallboard authentication

Configure local Wallboard authentication settings for the current authentication service.

Wallboard uses the same authentication model as other applications that use the same UCC service. When AnywhereNow Authentication is enabled for the UCC service, local clients such as Wallboard still require local client configuration.

## Before you begin

Confirm the following before you configure Wallboard authentication:

* Complete the shared [Configure Authentication](/platform-administration/provisioning/provisioning/configurations/configure-authentication.md) prerequisite.
* Confirm that the app registration redirect URI includes:

  ```
  https://login.anywhere365.cloud/auth/realms/<GUID>/broker/oidc/endpoint
  ```
* Confirm that the intended Wallboard users exist in Microsoft Entra ID.
* Back up the local `Config.xml` file before editing it.

Use this current client authentication URL format in Wallboard configuration:

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

Use `https://auth.anywhere365.cloud/auth/realms/<GUID>` only when following the [Authentication Migration](/operate/maintain-and-change/authentication-migration.md) path for an existing legacy configuration.

## Configure local authentication settings

In `Config.xml`, configure these local settings when AnywhereNow Authentication is used:

```xml
<Credentials enabled="false" username="" password="" />
<FeatureToggleAccessControl enabled="true" />
<FeatureToggleAccessControlUrl enabled="true" value="https://login.anywhere365.cloud/auth/realms/<GUID>" />
```

Replace `<GUID>` with the tenant identifier supplied for the customer.

## Validate authentication

After you update `Config.xml`:

1. Save the file.
2. Restart Wallboard from the installed shortcut.
3. Confirm that the user can sign in through the configured authentication URL.
4. Confirm that Wallboard connects to the configured UCC and loads the expected default view.

If the customer is migrating from the legacy authentication platform, complete the migration steps in [Authentication Migration](/operate/maintain-and-change/authentication-migration.md) before treating the local client update as complete.


---

# 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/wallboard/configure-wallboard-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.