Custom Connector

Custom Connector is a user system type that (depending on the system priority) allows:

  • Updating a database and from there an external system with personal data and resources from Compliance Suite based on roles (through Custom Resources) [Outbound].

  • Update Compliance Suite with personal data and roles (through Custom Keys) from a database containing data from an external system [Inbound].

The Custom Connector makes it easier and faster to build integrations between external systems and Compliance Suite. This is done via the Compliance Suite’s Connector Database.

The Custom Connector contains UPN and ObjectID for all identities of persons. For example, it can be used in Powershell scripts to uniquely identify a user object, such as in ADDS or Entra ID.

Custom Connector PowerShell module

The Custom Connector PowerShell module contains a number of commandlets that make it easier to update to and from the Custom Connector Database. These commandlets communicate with the database via a secure SQL connection (ports 1433, 1434).

You can learn more about the PowerShell module here.

Resource Role Importer

The Resource Role Importer table is used to import resources, roles and accesses into Compliance Suite from an external system, such as UBW.

Tables

CustomConnector_ResourcesRolesImport (used Inbound only)

  • ID

  • ResourceName,

  • ResourceTypeName,

  • ResourceTypeId,

  • ResourceCustomId,

  • ResourceStatus (active/inactive)

  • RoleName,

  • RoleCustomId (The role in Dynamics 365 is extended with this field)

  • RoleDescription,

  • RoleSelfServiceDisplayHelpText

  • RoleSelfServiceDisplayName

  • RoleUserCanRequest

  • RoleApprover (matches on MatchField specified in the system)

  • ResourceStatus (active/inactive)

  • ApplicationName,

  • ApplicationCustomId,

  • CreatedTime,

  • ModifiedTime,

  • Handled

CustomConnector_Accesses

  • ID,

  • PersonId,

  • RoleName

  • RoleCustomId

  • ApplicationName

Functionality

CustomConnector_ResourcesRolesImport

This table is not related to the person table. Resources: The type must already exist and only works on import. If the resource does not exist, it will be created. If it exists, the status of the resource will be updated.

They match as follows:

  1. Match on ResourceCustomId and System, if not found, then:

  2. Match on ResourceName, ResourceTypeName, and System, if not found, the resource will be created.

Roles: The application must already exist. Only works in case of import. If the role does not exist, it will be created. If it exists, the status of the resource will be updated.

They match as follows:

  1. Match on RoleCustomId, if not found, then:

  2. Match on RoleName and ApplicationName,, if not found, then:

  3. Match on RoleName

Linking role and resource: Only works in case of import. If both role and resource are specified in the same row (creation or update), the role is set on the resource if this has not already occurred.

CustomConnector_Accesses

Works in the same way as the Keys table, i.e. it refers to the person table.

Accesses: Assigns the role (access) to the person for each line. Only works in case of import. Finds the role based on the following order of priority:

  • Matches on RoleCustomId, otherwise

  • Matches on ApplicationName and RoleName, otherwise

  • Matches on RoleName