Single Sign On (SSO) Set Up

Dotcom-Monitor supports SSO login using SAML 2.0.

Here are the steps required to enable SSO with Active Directory FS (ADFS) and AZURE Active Directory (Azure AD) as the Identity Providers. Also, the step-by-step guides for OKTA SAML integration are provided.

SSO with Active Directory FS
1. Install ADFS 2.0 (help can be found at http://www.microsoft.com/en-us/download/details.aspx?id=10909).

2. Download metadata.xml.

3. In the ADFS 2.0 Management console, add an SSL certificate to sign Dotcom-Monitor responses/requests:
- Launch the ADFS 2.0 Management console and open Server Configuration Wizard.
- Click Create new FS and select Standalone FS.
- Select SSL certificate (if there are no certificates you can create self-signed cert using INETMGR > Server certificates > Create self-signed cert).
4. In the ADFS 2.0 Management console, add IDR to the ADFS Relying Party Trusts:
- Click Relying Party Trusts and select Add Relying Party Trust.
- In the wizard window, click Start and select Import data about the relying party from a file.
- Choose metadata.xml.
- Choose any meaningful name (dotcom-monitor.com).
- Click Next and follow the prompts.
- On the Issuance Authorization Rules step, select Permit all users to access this relying party
- On the finish, step click to deselect the Open the Edit Claim Rules dialog for this relying party trust when the wizard closes checkbox.
- Close the wizard.
5. Set SHA-1 as a secure hash algorithm:
- After creating relying party trust right-click it in the list and select Properties.
- Go to the Advanced tab and change the hashing algorithm to SHA-1.
6. Add claim rule to send LDAP attributes as claims:
- Right-click the relying party, select Edit Claim Rules.
- Click Add Rule and make sure the Claim rule template has Send LDAP Attributes as Claims selected.
- Give the Claim rule name.
- Select the Attribute store to be Active Directory.
- Add two attribute mappings: for User-Principal-Name set UPN, for Token-Groups – Unqualified Names set Role.
7. Add custom rule:
- Right-click the relying party, select Edit Claim Rules.
- Click Add Rule and set the Claim rule template to Send claims using custom rule.
- Give the Claim rule name.
- Insert the following script:
c:[Type == “http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn”] => issue(Type = “http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier”, Issuer = c.Issuer, OriginalIssuer = c.OriginalIssuer, Value = c.Value, ValueType = c.ValueType, Properties[“http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/format”] = “urn:oasis:names:tc:SAML:2.0:nameid-format:transient”, Properties[“http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/namequalifier”] = “http://www.example.com/adfs/services/trust”, Properties[“http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/spnamequalifier”] = “https://userauth.dotcom-monitor.com/”)
- Replace “http://www.example.com/adfs/services/trust” with the proper Identity Provider (IdP) entityID (“http://idpsite.com/adfs/services/trust“).
8. Open URL in browser from IdP machine: https://localhost/federationmetadata/2007-06/federationmetadata.xml

9. Save the XML content as a file and send it to Dotcom-Monitor support using the ticket system.

When SSO is enabled you can add Dotcom-Monitor website users by creating new users in AD or adding existing users to one of the following groups: “Dotcom-Monitor_Power_Users“, “Dotcom-Monitor_User_Users“, “Dotcom-Monitor_Accounting_Users“, “Dotcom-Monitor_ReadOnly_Users“, “Dotcom-Monitor_Operators“. Each of these groups must have the “global” or “universal” scope and the “security” type.
SSO with AZURE Active Directory
1. Log in to the Azure portal as a Global Administrator or Co-admin.

2. In the portal, on the left navigation panel, select Azure Active Directory.

3. To manage (create) users for the future SSO login using Azure AD, under the Manage section in the Azure Active Directory navigation panel, select Users > All users:

https://portal.azure.com/#blade/Microsoft_AAD_IAM/UserManagementMenuBlade/Overview/menuId/

4. Create a new enterprise application:
- In the Azure Active Directory navigation panel, select Enterprise applications.
- Click New Application, then Non-gallery application.
- On the Add your own application page, set the name for the new application (“userauth.dotcom-monitor.com”) and click Add.
https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/Overview/menuId/

5. Edit application metadata to add dotcom-monitor groups:
- In the Azure Active Directory navigation panel, select App registrations.
https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps
- Click the “userauth.dotcom-monitor.com” application, then under the Manage section, select Manifest.
- In the web-based manifest editor, add the following roles under appRoles node and Save:
```
    {
      "allowedMemberTypes": [
        "User"
      ],
      "displayName": "Dotcom-Monitor_Power_Users",
      "id": "b9632174-c057-4f7e-951b-be3adc52baaa",
      "isEnabled": true,
      "description": "Dotcom-Monitor_Power_Users",
      "value": "Dotcom-Monitor_Power_Users"
    }, 
    {
      "allowedMemberTypes": [
        "User"
      ],
      "displayName": "Dotcom-Monitor_Users",
      "id": "b9632174-c057-4f7e-951b-be3adc52babc",
      "isEnabled": true,
      "description": "Dotcom-Monitor_Users",
      "value": "Dotcom-Monitor_Users"
    }, 
    {
      "allowedMemberTypes": [
        "User"
      ],
      "displayName": "Dotcom-Monitor_Accounting_Users",
      "id": "b9632174-c057-4f7e-951b-be3adc52bbbb",
      "isEnabled": true,
      "description": "Dotcom-Monitor_Accounting_Users",
      "value": "Dotcom-Monitor_Accounting_Users"
    },
    {
      "allowedMemberTypes": [
        "User"
      ],
      "displayName": "Dotcom-Monitor_ReadOnly_Users",
      "id": "b9632174-c057-4f7e-951b-be3adc52bccc",
      "isEnabled": true,
      "description": "Dotcom-Monitor_ReadOnly_Users",
      "value": "Dotcom-Monitor_ReadOnly_Users"
    },
    {
      "allowedMemberTypes": [
        "User"
      ],
      "displayName": "Dotcom-Monitor_Operators",
      "id": "b9632174-c057-4f7e-951b-be3adc52bddd",
      "isEnabled": true,
      "description": "Dotcom-Monitor_Operator_Users",
      "value": "Dotcom-Monitor_Operator_Users"
    },
```
5. Edit SSO settings:
- In the Azure Active Directory navigation panel, select Enterprise applications, click All application.
https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/AllApps/menuId/
- Click the “userauth.dotcom-monitor.com” application.
- Under the Manage section, select Single sign-on.
- Select SAML to configure single sign-on. On the Set up Single Sign-On with SAML – Preview page configure the basic SAML options:
```
Identifier: “https://userauth.dotcom-monitor.com/” 
Reply URL: “https://userauth.dotcom-monitor.com/Login.ashx”
Unique User Identifier: “user.userprincipalname”
```
- Select the Edit icon (a pencil) in the upper-right corner of the User Attributes and Claims section and add the new attributes:
```
 Name: “Roles”
 Value: “user.assignedroles”
```
- Select the Edit icon (a pencil) in the upper-right corner of the SAML Signing Certificate section.
- In the SAML Signing Certificate section click Download Metadata XML and save it to the disk. This file must be sent to dotcom-monitor.com support.
- Check Make new certificate active ( only after downloading metadata ) and confirm the action.
- Check Show advanced certificate signing settings and set SHA-1 as the signing algorithm.
- Click Save.
6.Assign roles:
- In the Azure Active Directory navigation panel, select Enterprise applications, click All application.
https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/AllApps/menuId/
- Click the “userauth.dotcom-monitor.com” application, then select Users and groups.
- Click Add user, select user, select role (one of dotcom-monitor roles), click Assign. Do it for all users needed.
7. Send metadata.xml to dotcom-monitor support. Click here, login into your account and submit a ticket.
SSO with OKTA

Check the following materials to configure OKTA integration with Dotcom-Monitor and enable SSO:

OKTA – Dotcom-Monitor Integration PDF Guide

OKTA SAML Integration with Dotcom-Monitor Walkthrough Video

SAML Login Video

See also the following alternative guides:

Okta to Dotcom-Monitor Alternative Guide

Okta to Dotcom-Monitor SAML Configuration Video

Configuring SSO for Departments

If you have a Department created for the Dotcom-Monitor account, you can configure SSO users logging in to it.

To enable SSO for Departments, add the department name as a suffix to the name of the group or role reserved for Dotcom-Monitor purposes in AD. Use a double hyphen as a separator:

<Group Name>–<Department Name>

For example, to allow a user to log in to the “AlphaDep” department as a Power User you need to add the following suffix to the Dotcom-Monitor_Power_Users AD Group:

«Dotcom-Monitor_Power_Users--AlphaDep»

To change an ADFS Group name, right-click the group and select Rename. Once renamed, change the pre-Windows 2000 name as well in the pop-up box or from Properties > General > Group Name (pre Windows 2000).

To enable SSO for several Departments simultaneously, add the department names one by one using the same format. For example:

«Dotcom-Monitor_Accounting_Users--AlphaDep--BetaDep--Department3»

To allow users logging in to the root account, specify a relevant AD Group without a department suffix as was described above:

«Dotcom-Monitor_ReadOnly_Users»

If a user is included in several «Dotcom-Monitor_» AD Groups with configured SSO for Departments, logging in to all corresponding Departments will be enabled (if the Departments exist in the Dotcom-Monitor account).

Single Sign On (SSO) Set Up

SSO with Active Directory FS

SSO with AZURE Active Directory

SSO with OKTA

Configuring SSO for Departments

Solutions

Features

Company