AnywhereNow Authentication Service for Inflight Wallboard

AnywhereNow Authentication service allows users to sign in with their own Office 365 credentials with AnywhereNow products. This authentication method provides not only convenience, but also greatly improves security.

Important

Snapper, Inflight Wallboard and WebWallboard all use the same authentication method per UCC A Unified Contact Center, or UCC, is a queue of interactions (voice, email, IM, etc.) that are handled by Agents. Each UCC has its own settings, IVR menus and Agents. Agents can belong to one or several UCCs and can have multiple skills (competencies). A UCC can be visualized as a contact center “micro service”. Customers can utilize one UCC (e.g. a global helpdesk), a few UCC’s (e.g. for each department or regional office) or hundreds of UCC’s (e.g. for each bed at a hospital). They are interconnected and can all be managed from one central location. service. In other words, if AnywhereNow Authentication is enabled for one application it is also enabled for the other applications using that service. The configuration of WebWallboard is handled by Dialogue Cloud, but if also Snapper and/or Inflight Wallboard are used, these client applications must each be configured for this method of authentication.

See AnywhereNow Authentication for Snapper

See AnywhereNow Authentication for Web Wallboard

As of bundle DC2024.01f a new Redirect URI (and backend platform) has been enabled and is required to be used. Please see: AnywhereNow Authentication Migration Guide.

Prerequisites

Having created an Azure App Registration for your AnywhereNow product according to the procedure described in Create new Azure App Registration for AnywhereNow Authentication.
An AnywhereNow Authentication URL provided by AnywhereNow.

This URL should be similar to this example: https://auth.anywhere365.cloud/auth/realms/<GUID GUID stands for Globally Unique Identifier (format is always like 2ed153b4-f632-4766-b846-5b2a769b36d1) and is a pseudo random number used in software applications that is assumed to be unique. The total number of unique keys (2<sup>128</sup> of 3.4028×10<sup>38</sup>) is very large and the probability of the creating the same GUID twice is very small, though not 100% guaranteed. The term GUID is generally used by developers working with Microsoft technologies, while UUID is used everywhere else.>

or from bundle DC2024.01f or later: https://login.anywhere365.cloud/auth/realms/<GUID> (please also see AnywhereNow Authentication Migration Guide)

Note

Replace <GUID> with the "AnywhereNow Tenant ID" provided by your AnywhereNow contact

To set up Inflight Wallboard to use AnywhereNow Authentication do the following:

Make sure the prerequisites have been fulfilled. See Prerequisites.
In the config.xml, go to the Normal Views settings:
- Change the Credentials enabled line to the following:
  Copy
  Credentials enabled
```
<Credentials enabled="false" username="" password="" />
```
- Set the following settings to the values shown. If these lines are not already present, add them yourself:
  Copy
  Feature toggle access control
```
<FeatureToggleAccessControl enabled="true" />
<FeatureToggleAccessControlUrl enabled="true" value="[AUTHENTICATION URL]" />
```
- Make sure all intended users are available in Microsoft Entra ID Formerly known as Azure Active Directory (or Azure AD, or AAD), as they would otherwise not be able to login to and open the Inflight Wallboard application.