Integrate ConnectWise Home

You con configure ConnectWise Home to use Identity as a Service for multifactor authentication. ConnectWise Home is a business process automation platform (see https://www.connectwise.com/). This integration provides instructions to integrate ConnectWise Home with Identity as a Service. Once integrated, users can use single sign-on to log in to their ConnectWise account using Identity as a Service

Note: This integration was tested using Identity as a Service version 5.30 and ConnectWise Home build 23.4.3.8545. Other versions of the ConnectWise Home may require integration and configuration steps that differ from those documented in this procedure. For other versions of ConnectWise Home, this integration guide may be used as an initial approach for integrating ConnectWise Home. In the event of other issues, contact support@entrust.com for assistance.

To integrate ConnectWise Home with Identity as a Service, you must do the following:

Before you begin, open two browser windows. In one window, log in to your ConnectWise Home administrator account. In the other window, log in to your IDaaS administrator account.

Step 1: Copy the Redirect URI from ConnectWiseStep 1: Copy the Redirect URI from ConnectWise

In ConnectWise, click to display the User & Applications Settings page.

In the navigation pane, click Authentication > Add Provider > Add Login Provider. The Add Login Provider page appears.

Copy and save the Redirect URI to a text file, such as Notepad.

Leave this page open. You return to it in Step 5: Add IDaaS to ConnectWise Home.

Step 2: Add ConnectWise Home OIDC to Identity as a ServiceStep 2: Add ConnectWise Home OIDC to Identity as a Service

In IDaaS, click > Security > Applications. The Applications List page appears.

Click Add. The Select an Application Template page appears.

Do one of the following:

Select OpenID Connect and OAuth Cloud Integrations from the search drop-down list and scroll to find the application you want to add to IDaaS.

- or -

In the Search bar, enter a search option to filter for the application you want to add to IDaaS.

Click ConnectWise Home. The Add ConnectWise Home page appears.

Modify the Application Name and Application Description, if required.

Optional. Add a custom application logo, as follows:

Click next to Application Logo. The Upload Logo dialog box appears.

Click to select an image file to upload.

Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.

If required, resize your image.

Click OK.

Select the following as the Authentication Flow that appears to users during login.

Enable user login

Enable Identity Providers

Click Next. The General Settings and Authentication Settings page appears.

In the General Settings, do the following:

Copy and save the Client ID in a text editor, such as Notepad. You need this value for Step 5: Add IDaaS to ConnectWise Home.

Select the OIDC Signing Certificate used to connect to ConnectWise Home.

Optional: Deselect Show Login Redirect URL in My Profile to hide the application from a user's profile.

In the Initiate Login URI field, enter https://home.connectwise.com.

Click Add next to Login Redirect URIs.

In the Add Login Redirect URI field, enter the Redirect URI that you copied in Step 1: Copy the Redirect URI from ConnectWise and then click OK.

Optional: Select Respond Immediately for Unsuccessful Responses to return to the application immediately after a login failure, rather than allow user to try again with a different userID.

Deselect Enable Go Back Button if you do not want users to be able to go back to the ConnectWise OIDC login page to log in.

Accept the defaults for the remaining General Settings.

In the Authentication Settings, do the following:

Select Require Content to require that users respond to a consent prompt for each request.

Optional. Enter a Consent Message to include a message to users when consent is requested.

Set Max Authentication Age (seconds) to the maximum amount of time that can elapse before a user must re-authenticate to log in. This feature is disabled if the field is left blank.

Under Grant Types, select Implicit. The Grant Type tells Identity as a Service what flow to use for returning authorization responses.

From the Authorization Code PKCE Code Challenge Method drop-down list, select None as the method used with PKCE during authentication.

Do not select Include Authentication Time to include the authentication time for all tokens.

From the ID Token Signing Algorithm drop-down list, select RS256 as the signing algorithm used to sign with ID Token during authentication.

From the User Info Signing Algorithm, select RS256.

The authorization request uses Supported Scopes to establish a connection between Identity as a Service and the ConnectWise OIDC application. Supported Scopes are selected by default. If you disable Your unique identifier, the ConnectWise OIDC application strictly uses an access token to access a resource server API on behalf of a user.

Note: Click the arrow next to each scope to see the list of Implied Claims included in the scope. The list of Implied Claims is defined by OpenID Connect and cannot be modified. Every Implied Claim included in the scopes you select under Supported Scopes should have an associated Identity as a Service user attribute so that the attribute is returned as part of the OIDC tokens sent back to the client. For example, if you select Address as a Supported Scope, then you must define an Identity as a Service user attribute for each Implied Claim associated with Address. See Create and manage user attributes.

Do not modify any of the Supported Claims selected settings.

Click Submit.

Step 3: Add a resource ruleStep 3: Add a resource rule

See Create resource rules.

Step 4: Optional. Add a resource serverStep 4: Optional. Add a resource server

Manage OAuth authorization with a resource server.

Add an API/URL resource server

Click > Security > Authorization. The Authorization page appears.

Select API/URL to add a protected resource. The APIs/URLs list page appears.

Click . The Add API/URL page appears.

Under Basic Definition, do the following:

Select Enabled to make this API/URL resource active in Identity as a Service. JWT access tokens will not be issued unless the authorization is active.

Enter a Name for the resource.

Enter a Description for the resource.

Add a Value for the resource. The value should be an absolute URI value. The value corresponds to the API (aka audience value) that the resource server is protecting.

Note: The API/URL names and values must be unique across all resource server.

Select the Supported OIDC/OAuth Applications from the drop-down list. These are the applications that have permission to access the resource server. If you want all OIDC and OAuth applications to access the resource server, leave this field blank.

Under Token Definition, do the following:

Select Require Consent to prompt users for consent when an OAuth token is requested.

Select Include Application Name to include the application name in OAuth access tokens.

Select Include Client ID to include the client ID in OAuth access tokens.

Select Include OIDC Scopes and Claims to include the claims derived from OIDC scopes and claim requests in OAuth access tokens.

Select Include Authentication Claims to include authentication claims in OAuth access tokens.

Select Include Transaction Claims to include the transaction details in OAuth access tokens (for applications using the JWT IDaaS grant type).

From the Access Token Signing Algorithm drop-down list, select the signing algorithm that is used to sign the access tokens during authentication.

Set the Access Token Timeout to the time that the access token is valid before it expires.

Select Refresh Token to allow refresh token requests for OAuth token access. If you select this option, complete the following:

Set the Refresh Token Timeout to the time that the refresh token associated with the access token is valid.
Set the Refresh Token Limit to the maximum amount of a time a refresh token process is valid.

Under Scope Configuration, add the scopes (the permissions) the OIDC and OAuth application can request on behalf of the user for the configured API/URL (for example, view:calendar, edit:calendar). To add scopes:

Select Allow All Scopes to be requested to allow client applications to use the specific scope all_scopes to request all scopes the user has access to for this API/URL. This is a short-hand mechanism to request all scopes instead of listing out all scopes in the request.

Select Role-Based Access Control (RBAC) to enable access to scopes based on their Access Management Role associations. If disabled, the user has access to all scopes associated with the API/URL regardless of their Access Management Role. When enabled, the user only has access to the scopes permitted by the Access Management Role associations. To create RBAC, see Configure Role-Based Access Control (RBAC ).

Click Add. The Add Scope dialog box appears.

Add a Name for the scope.

Add a Value for the scope, for example, edit:calendar.

Click Add.

Note: Scope names and values must be unique across scopes defined across all APIs/URLs.

Click Save.

Step 5: Copy the OIDC configurations from IDaaSStep 5: Copy the OIDC configurations from IDaaS

In IDaaS, click > Resources > Applications. The Applications List page appears.

Under OpenID Connect and OAuth Integrations, click OIDC Configuration.

Copy the Issuer URL to a text file, such as Notepad.

Click OK to close the OIDC Configuration dialog.

Step 6: Add IDaaS to Connect WiseStep 6: Add IDaaS to Connect Wise

Return to the ConnectWise Home browser window that displays the Add Identity Provider page.

Enter a Display Name, for example, EntrustOIDC.

Enter the Client ID you copied in Step 2: Add ConnectWise Home OIDC to Identity as a Service.

In the Authority URL field, enter the Issuer URL you copied in Step 4: Copy the OIDC configurations from IDaaS.

In the Response Type drop-down list, select id_token.

Click the Users List tab. The Add Login Provider page appears.

Check Select All.

Click Save. The Connect Wise Configuration Details appear.

Step 7: Test the integrationStep 7: Test the integration

Test the integration between your ConnectWise Home and Identity as a Service accounts to confirm that your settings have been configured correctly.

Test Service Provider Login

Open a Web browser and enter the URL for your ConnectWise Home account.

Click Sign in with ConnectWise.

Enter your ConnectWise Home account email address and then click Next. You are redirected to Identity as a Service.

Enter your IDaaS user ID and then respond to the second-factor authentication.

Click Accept on the dialog box.

Test Identity as a Service redirect log in.

Go to your My Profile page if you are not already there.

Under Applications, click ConnectWise Home OIDC.

Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to ConnectWise Home.