How to Encrypt the SQL CDR Connection Strings

Introduction

With AnywhereNow you can encrypt various individual parts of your SQL Connection String for your CDR Call Detail Records (CDR) are the meta data of a converstation: who talked to whom, at which time, for how long and with which identity among other things (skill, optional classification, etc) which gets stored in your SQL (analytical) database. Connection information. This allows you to encrypt the "values" part of each Connection String element (like Servername, UserId, Password, etc.) to mask them from immediate visibility on a SharePoint page, which may be visible to other users.

Warning

The Encrypted Connection String will only work on the SharePoint field CDRConnectionString in the Settings menu to be used by the 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. Core.

It will not work for any of the other UCC services like CallPropertyService, UniversalTimelineService, DialogueManager, WebAgentSettings.

Read more, for advised procedure using encrypted ConnectionString via OnePortal

To have the least amount of downtime when creating a new UCC using OnePortal Formerly known as Partner Portal. A redesigned web portal for managing Dialogue Cloud deployments., our advice is to create the UCC site in SharePoint with encrypted CDRConnectionString and through OnePortal create and start-up the UCC first. This will also populate the internal settings (not managed through SharePoint) for CallPropertyService (CPS) and UniversalTimelineService (UTL) with the encrypted variant of the ConnectionString. As a next step the plain-text variant of your ConnectionString can then be set/corrected in OnePortal for CPS and UTL.

TIP: As of DC2025.01, a more comprehensive method of storing and hiding credentials from SharePoint views like SQL ConnectionStrings for various services, can be enabled using Secure Vault, only available in OnePortal. See: Dialogue Cloud Secure Vault.

Find Encrypted Tokens list

1. Open your UCC config site on SharePoint

2. Open Settings (top-right)

3. Open Site contents

4. Open the EncryptedTokens list

   • The following columns should exist.

     1. Title

        1. Name: Title

        2. Type: Single line of text

     2. Key

        1. Name: wsp_ucc_et_key

        2. Type: Single line of text

     3. Value

        1. Name: wsp_ucc_et_value

        2. Type: Single line of text

Add Encrypted Token(s)

1. Open the EncryptedTokens list

2. Add + new item:

   1. Title: "Enter any unique name as a title" example: SqlCdr password 1

   2. Key: "Technical key name in {} brackets", example: {encryptedTokenKeyName1}

   3. Value: "Encrypted string of the original value" example: xoZ9HvpaP5eGPALVdZzVJA== (Created with A365.PWTool.exe)

Encrypt CDRConnectionString

Single value encrypted as token

1. Open Settings list

2. Edit CDRConnectionString

   Copy

   Connectionstring

   Server=myServerName\myInstanceName;Database=myDataBase;User Id=myUsername;Password=myPassword;

3. Change to

   Copy

   Connectionstring

   Server=myServerName\myInstanceName;Database=myDataBase;User Id=myUsername;Password={encryptedTokenKeyName1};

Your myPassword value is now stored in SharePoint (and the UCC) only as an encrypted value.

Multiple values encrypted as token

You can have multiple encrypted tokens in 1 connection string.

Server={encryptedTokenKeyName1};Database={encryptedTokenKeyName2};User Id={encryptedTokenKeyName3};Password={encryptedTokenKeyName4};