SAML 2.0 Configuration

Device42 integrates with SAML 2.0 in conjunction with AD or LDAP user synchronizations to provide Single Sign On (SSO) support in Device42. Once users are added to Device42 via Active Directory or LDAP, they will automatically be logged into Device42 when they load the site.

Note Since authorization is handled by Device42, the user needs to exist within Device42 before they can log in for single sign on functionality to work.

SAML configuration varies between providers, but we’ll provide the steps for configuration with Microsoft ADFS, Okta and Onelogin below as examples. Device42 SSO should also work with any SAML2.0 compatible Identity Provider, and has been confirmired working with IDaaS providers Centrify and PingIdentity’s PingOne and PingFederate as well.

Should you need further assistance, please contact Support.

Microsoft ADFS Configuration

Add new relying party trust.

ADFS Party Trust

Next screen : Add data manually.

ADFS Party Trust

Next screen : Specify your app display name.

Next screen : Choose AD FS profile.

Next screen : Choose SAML 2.0 SSO and set proper D42 ACS url – https://___device42___url/saml2_auth/acs/.

Next screen : Set identifiers access – https://___device42___url/saml2_auth/acs/.

Next screen : Permit all users

Next screen : In claims section ( click “edit claims” on relying party / automatic go to this section after initial setup ), add the following claims

username claim

ADFS Party Trust

nameid claim

ADFS Party Trust

Copy metadata url from endpoints

ADFS Party Trust

** if you receive time synchronization error please write this command in powershell :
Set-ADFSRelyingPartyTrust -TargetIdentifier “” -NotBeforeSkew 5

Azure AD Configuration

1. Navigate to Azure AD in the Azure portal > Enterprise Applications > New Application > Create your own application. Give your app a name (the app shown in the screenshots is Device42SAML) and select the third option Integrate any other application…, then click Create.

2. Open your newly created enterprise app > Option 2- Set up Single sign on, or select Single sign-on under Manage in left-hand toolbar.

3. Enter https://<D42-FQDN-or-IP>/saml2_auth/acs in Identifier (Entity ID) and Reply URL (Assertion Consumer Service URL) in Section 1 Basic SAML Config.

4. Navigate to the Device42 Appliance Manager > Global Settings > SAML 2.0 Settings. Copy the App Federation Metadata URL in the SAML Signing Certificate section from the enterprise app you created in Azure AD and paste into Metadata auto conf url in the D42 Appliance Manager.

5. While still in the SAML 2.0 settings of the Appliance Manager, enter http://schemas.xmlsoap.org/ws/2005/05/identity/claims/SAML_Attribute to map the Azure AD value to the appropriate SAML attribute. Save and restart the appliance from the VM console menu with option 4. You may wish to complete steps 6 and 7 before saving/restarting so that you can still login to D42 and create users with the local admin account you’ve used so far.
The SAML attributes tested successfully are listed below-

  • emailaddress– Email address associated with user account in Azure AD
  • name– User Principal Name (UPN) associated with user account in Azure AD

6. Assign users/groups to the SAML enterprise app you created in Azure AD. These should be users/groups that you want to allow authentication into Device42 via this SAML integration.

7. For any users associated with the enterprise app in Azure AD, create the user in Device42 using the appropriate Azure AD value with a dummy password. The integration does not pull and create users directly from Azure AD, so the users must be created within Device42 prior to any attempt to authenticate via Azure AD.

8. Once the above has been completed, you should be able to login to your D42 instance with your Azure AD credentials.

Okta Configuration

In Okta, click the “Admin” button:

Okta Admin Link

Click “Applications” button

Okta Applications Link

In the “Applications” page find “Add application” button and click it.

Okta Admin Link

Choose “Create new app”

Okta Admin Link

Select platform as Web and sign on method as SAML 2.0.

Okta Admin Link

Set application preferences and click next

Okta Admin Link

On the next page setup ACS url and field mapping. The Single Sign On URL & Audience URI should be https://yourdevice42address/saml2_auth/acs/. The Attribute value should be the same AD or LDAP attribute that your users will log into Device42 with. Note the “Name” given to it as this will be needed in the Device42 Appliance Manager configurations.

Okta Admin Link

Click “Next” and finish setup.
Open your application settings, go to the “Sign On” tab and copy url from “Identity provider metadata” link. This will be used as the “Metadata URL” in Device42’s Appliance Manager.

Okta Admin Link

Onelogin Configuration

Create and login into your OneLogin account.
Create an app connector in OneLogin
Go to Apps > Add Apps.

Okta Admin Link

Search for SAML Test Connector.
Select the SAML Test Connector (IdP w/ attr) app.

Okta Admin Link

Save.
Open new application and go to the “Configuration” tab, set the Audience, Recipient and ACS URL values to https://yourdevice42address/saml2_auth/acs/

Okta Admin Link

Click “SSO” tab, and copy “Issuer URL”. This will be entered in the “Metadata URL” field in Device42.

Okta Admin Link

Click “Save”

Device42 Appliance Manager Configuration

Login to Device42 Appliance Manager, https://yourdevice42address:4343, and go to the SAML 2.0 settings on the left, then set metadata url you obtained above. Set the “username” field to match the value you saved in the SAML configuration.

Okta Admin Link

After this has been saved, SAML integration should be complete!