Step 1: Copy
the Redirect URI from ConnectWiseYou 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.
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 ConnectWise1. In ConnectWise, click 
to display the User & Applications
Settings page.
2. In the navigation pane, click Authentication > Add Provider > Add Login Provider. The Add Login Provider page appears.
3. Copy and save the Redirect URI to a text file, such as Notepad.
4. 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 Service1. In IDaaS, click 
> Security > Applications.
The Applications List page appears.
2. Click Add. The Select an Application Template page appears.
3. Under OpenID Connect and OAuth Cloud Integrations, click ConnectWise Home. The Add ConnectWise Home page appears.
4. Modify the Application Name and Application Description, if required.
5. Optional. Add a custom application logo, as follows:
a. Click 
next
to Application Logo. The Upload
Logo dialog box appears.
b. Click 
to select an image file to upload.
c. Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.
d. If required, resize your image.
e. Click OK.
6. Select the following as the Authentication Flow that appears to users during login.
● Enable user login
● Enable Identity Providers
7. Click Next. The General Settings and Authentication Settings page appears.
8. In the General Settings, do the following:
a. 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.
b. Select the OIDC Signing Certificate used to connect to ConnectWise Home.
c. Optional: Deselect Show Login Redirect URL in My Profile to hide the application from a user's profile.
d. In the Initiate Login URI field, enter https://home.connectwise.com.
e. Click Add next to Login Redirect URIs.
f. 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.
g. 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.
h. 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.
i. Accept the defaults for the remaining General Settings.
9. In the Authentication Settings, do the following:
a. Select Require Content to require that users respond to a consent prompt for each request.
b. Optional. Enter a Consent Message to include a message to users when consent is requested.
c. 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.
d. Under Grant Types, select Implicit. The Grant Type tells Identity as a Service what flow to use for returning authorization responses.
e. From the Authorization Code PKCE Code Challenge Method drop-down list, select None as the method used with PKCE during authentication.
f. Do not select Include Authentication Time to include the authentication time for all tokens.
g. From the ID Token Signing Algorithm drop-down list, select RS256 as the signing algorithm used to sign with ID Token during authentication.
h. From the User Info Signing Algorithm, select RS256.
10. 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.
11. Do not modify any of the Supported Claims selected settings.
12. Click Submit.
Step 3: Add
a resource rule to protect access to ConnectWise HomeCreate a resource rule to protect access to OIDC applications
1. Log in to your Identity as a Service administrator account.
2. Click
> Security
> Resource Rules. The Resource Rules List
page appears.
3. Click + next to the application you want to protect with a resource rule. The Add Resource Rules page appears.
4. Enter a Rule Name and Rule Description for the resource rule.
5. In the Groups list, select the group or groups of users restricted by the resource rule.
These are the groups to which the resource rule applies. If you do not select any groups, by default the resource rule applies to all groups.
6. Click Next. The Authentication Conditions Settings page appears.
7. Optional: Select Disable Single Sign-On for Application to force a user to re-authenticate whenever they attempt a new login.
8. If you do not Enable Advanced Risk Factors, do the following:
a. Select the Authentication Flow from the drop-down list. The Authentication Flow flowchart updates based on the selection.
b. Click Submit to save the Resource Rule.
9. If you want to Enable Advanced Risk Factors, complete the remaining steps in this procedure.
10. Select Enable Advanced Risk Factors to add additional risk factors to the resource rule.
11. Select Enable Strict Access for Application to set the resource rule to deny access regardless of the outcome from other resource rules. If this option is disabled for any resource rule that denies access, the user is allowed access if at least one resource rule allows access.
12. For each Advanced Risk Factor, click the Deny option to deny access to the application if the risk factor fails regardless of the results of the other risk factors.
13. Click Date/Time to set the conditions as follows:
a. Select one of the following:
– Allow Date/Time to set when a user can access the application.
– Deny Date/Time to set when the user cannot access the application.
The Date/Time Context Condition Settings appear.
b. Select the Condition Type:
– Specific Date Range Condition—Allows or denies access to the application during a select period of days.
– Time-of-day and/or Day of Week Recurring Conditions—Allows or denies access to the application on a specific time of day, day of the week, or both. Recurring times selected only apply to days not denied.
– Clear Selection—Clears existing Date and Time conditions.
c. Set the Condition Type settings, as follows:
i) Select Use local time zone to use the local time zone or deselect Use local time zone to use the local time zone and begin typing the time zone in the Begin Typing Timezone name field and select the time zone from the drop-down list.
ii) If you selected Specific Date Range Condition, click Start Date to select a start date from the pop-up calendar. Optionally, select the End Date.
iii) If you selected Time-of-Day and/or Day-of-Week, click Start Time and select the start time from the pop-up clock. Optionally set the End Time. You must also select the days of the week for the condition.
d. Click Save to return to the Authentication Conditions Settings page.
14. Click Geolocation to set the Location Condition Settings, as follows:
a. Select Allow or Deny to create an allowed or denied country list.
b. From the Selected Countries drop-down list, select the countries to add or deny access to the application. Repeat until you have added all the desired countries to the list.
c. Select Allow Anonymous IP Address to increase the risk of users authenticating from an anonymous IP.
d. Click Save to save to return to the Authentication Conditions Settings page.
15. Click Source IP Address. The IP Address Risk Setting dialog box appears. Do one of the following:
a. Select Custom and add the required IP Allowed Addresses and IP Denied Addresses.
b. Select IP List Address and select the IP List to allow or deny.
c. Select None to not restrict any IP addresses.
d. Click OK to return to the Authentication Conditions Settings.
16. Click Machine Authentication to set the Machine Authentication Condition Settings, as follows:
a. Set the Machine Authentication Risk is less than or equal to the value that the machine authenticator's total risk score must be less than during authentication to pass this condition.
The risk score is based on the attribute differences
between a user's Machine Authentication information and that recorded
on Identity as a Service before the condition fails. If an attribute does
not match, the attribute incurs the number of risk points shown in Non-Matching Risk Points for that attribute. The
Non-Matching Risk Points values of each non-matching
attribute are added together, resulting in a total risk score. This score
is normalized to be out of 100 as follows:
Total Risk Score = (Total Risk Points
of Failing Attributes / Maximum Risk Points of All Enabled Attributes)
* 100
The resource rule condition fails when the number of non-matching risk
points exceeds the Machine Authentication Risk value defined in this step.
A value of 0 means that a single attribute
difference causes the Device Fingerprint
condition to fail. The default value is 3.
The value between 0-50 can be entered.
The default value is defined by the Machine Risk Limit.
See Modify machine authenticator settings.
b. Click Save.
17. Define the Location History / Known Locations and Travel Velocity conditions. The Risk-Based Authentication (RBA) settings of your Identity as a Service account define the location history and travel velocity conditions. See Manage risk-based authentication settings for more information.
18. Set the Device Certificates risk factor to require the client to perform client-authenticated SSL with a certificate issued from a trusted CA to pass.
19. Set the risk score for application conditions to set the risk percentage a user receives if they fail to meet the condition, as follows:
● Click the dot next to the condition setting and slide the risk scale to the risk percentage
-or-
● Click the 0% and enter the risk points and then click OK.
The default setting is 0%. The Risk percentage determines the authentication requirements as set by the Authentication Decision. When a user attempts to authenticate to an application, the final risk percentage is the sum of all failed conditions.
20. Set the Authentication Decision risk level for Medium Risk and High Risk as follows:
a. Click the risk threshold percentage to the right of Medium Risk or High Risk. The Risk Threshold dialog box appears.
b. Enter the risk percentage.
c. Click OK.
21. Select the Authentication Flows for Low Risk, Medium Risk, and High Risk from the drop-down lists. The Authentication Flows flowchart updates based on your selections.
22. Click Submit to create the resource rule.
Step 4: Copy
the OIDC configurations from IDaaS1. In IDaaS, click
> Resources > Applications.
The Applications List page appears.
2. Under OpenID Connect and OAuth Integrations, click OIDC Configuration.
3. Copy the Issuer URL to a text file, such as Notepad.
4. Click OK to close the OIDC Configuration dialog.
Step 5: Add
IDaaS to Connect Wise1. Return to the ConnectWise Home browser window that displays the Add Identity Provider page.
2. Enter a Display Name, for example, EntrustOIDC.
3. Enter the Client ID you copied in Step 2: Add ConnectWise Home OIDC to Identity as a Service.
4. In the Authority URL field, enter the Issuer URL you copied in Step 4: Copy the OIDC configurations from IDaaS.
5. In the Response Type drop-down list, select id_token.
6. Click the Users List tab. The Add Login Provider page appears.
7. Check Select All.
8. Click Save. The Connect Wise Configuration Details appear.
Step 6: Test
the integrationTest 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
1. Open a Web browser and enter the URL for your ConnectWise Home account.
2. Click Sign in with ConnectWise.
3. Enter your ConnectWise Home account email address and then click Next. You are redirected to Identity as a Service.
4. Enter your IDaaS user ID and then respond to the second-factor authentication.
5. Click Accept on the dialog box.
Test Identity as a Service redirect log in.
1. Log in to your Identity as a Service Account.
2. Go to your My Profile page if you are not already there.
3. Under Applications, click ConnectWise Home OIDC.
4. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to ConnectWise Home.