SAML SSO for Solve
  • Dark
    Light
  • PDF

SAML SSO for Solve

  • Dark
    Light
  • PDF

When accessing Solve via a direct URL, you can configure SAML to enable Single Sign-On (SSO) authentication. The settings in Solve enable you to set up a trust relationship between the URL hosting Solve and your company's Identity Provider (IdP) so users can access Solve securely.

Here is an overview of what you have to do to configure SAML with detailed steps provided below.

  • Enter the required URLs from your IdP into the Solve settings page.
  • Upload a trust certificate from your IdP into the Solve settings page.
  • Download the trust certificate from the Solve page and add it into your IdP.
  • Retrieve the necessary fields from the Solve settings page and enter them into your IdP.

Below are the specific steps you have to perform regardless which IdP you use. 

Following this procedure, we have provided use cases and/or diagrams to demonstrate how to configure SAML/SSO in Solve for these specific Identity Providers:

To configure SAML in the Solve interface:

  1. In your chosen IdP, locate the trust certificate to use for Solve and copy it to a location accessible to the local computer from where you are accessing Solve.
  2. Open the ControlUp Real-Time Console.
  3. Access Solve from the Solve menu on the top ribbon of the Real-Time Console. The Solve interface opens in a browser window.
  4. In the Solve home page, click the settings link on the bottom of the menu on the left side of the window.
  5. In the Solve Settings page, turn the toggle button on for Enable SAML (SSO) Authentication.
Note

It is recommended not to enable both SAML and LDAP. If both are enabled, Solve uses SAML authentication.

  1. Enter the following URLs from your IdP:- IdP Login URL. The URL used for logging into your IdP.
    • IdP Logout URL. This is an optional field to use for signing out of the IdP. For example, if ADFS is the IdP, the URLs could look like this with your company's domain:
      360017672018SignURLsDomain.jpg
  2. Click IdP Signing Certificate and locate the certificate from your IdP that you copied in Step1.
  3. Enter the Entity/Issuer ID. The virtual server as configured in the IdP connection certificate.
    For example, the URL could look like this with your company's domain:
    360017618057VirtualServerIDsURL.jpg
  4. The Solve settings page provides you with the following values:
    • Relying Party Trust Identifier. The unique uniform resource name that is a persistent identifier.
    • Endpoint/Assertion Login URL. The endpoint that your IdP will use to redirect during the authentication process.
    • Assertion Logout URL .
      Here's an example of what these values could look like:
      360017652438SOLVEvalues.jpg
      Copy these values and enter them into the appropriate locations in your IdP.
  5. Under Solve Signing Certificate, click the certificate link to download the trust certificate for Solve and save it in a location that your IdP can access.
    360017600377SignRequest.jpg
    Now you can return to your chosen IdP and create an endpoint for Solve using the values provided and the downloaded certificate.

UPN assertion
Note that for any IdP, we assert the UPN and must match what the IdP presents, so we require the NameID attribute with the UPN value of the user. For example:
<NameID Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">The user created</NameID>


Use Case Example - Active Directory Federated Service (ADFS)

Read here to get the basic details of how to configure secure SAML authentication if your Identity Provider (IdP) is ADFS.

  1. Open your ADFS interface.
  2. Under the Service folder, click Certificates. Copy one of the certificates to a location accessible to the user configuring the SAML settings for Solve.
    360017623897ADFSCertificates.png
    This is step 1 from the generic steps above, and you upload this certificate in step 7 above.
  3. In the ADFS interface, select Relying Party Trusts . Right-click to open the Properties dialog.
    360017672258ADFSRelyingPartyTrustsMenuBlank.png
    ADFS Properties Dialog
  4. In the Properties dialog, select the Endpoints tab and click Add SAML... The Edit Endpoint dialog opens.
  5. Under the Trusted URL field, copy the Assertion URL you retrieved from the Solve Settings page in step 9 of the procedure above.
    360017672298ADFSAddEndpoint.png
    ADFS Edit Endpoint Dialog
    Ensure that:
    Endpoint type is SAML Assertion Consumer
    Binding is POST
  6. Click OK and this Endpoint is added.
    360017614677ADFSEndpointAdded.png
    ADFS - Endpoint Added
  7. In the same Properties dialog, select the Signature tab, click Add and upload the Solve certificate you downloaded in step 10 of the procedure above.
    360017620097ADFSSignature.png
    ADFS - Add Signature
  8. In the same Properties dialog, select the Identifiers tab, and under the Relying party identifier: field, enter the Relying Party Trust Identifier value you retrieved from the Solve Settings page in step 9 of the above procedure. Click Add next to the field and you'll see the URN added to the list of Relying party identifiers in the dialog.
    360017672938ADFSIdenfifiers.png
  9. Click the Relying Party Trusts folder, right-click the claim rule, and select Edit Claim Issuance Policy...
  10. In the Edit Claim Issuance Policy wizard, click Add Rule...
  11. In the Choose Rule Type wizard, select Send LDAP Attributes as Claims as the claim rule template and click Next.
  12. On the Configure Claim Rule screen, provide a Claim rule nameChoose Active Directory from the Attribute store dropdown menu. Under Mapping of LDAP attributes to outgoing claim types, select User-Principal-Name as an LDAP attribute and UPN for the outgoing claim type. Click Finish to save the rule.
  13. Confirm the new rule by clicking OK.

Your Solve users should now be able to authenticate through your ADFS identity provider.

Use Case Example - Azure Active Directory SAML

Prerequisites:

  • Must have an Azure Enterprise account.
  • Azure Active Directory (AD) must be configured.
  • Must have the necessary permissions to create the application.

Preparation on Azure AD

  1. In the Browse Azure AD Gallery, select Create your own application .
    4403304210961ScreenShot2021-06-23at105509AM.png
    Azure AD - App Creation Screenshot
  2. In the Create your own application page, enter a name of your choosing and select Integrate any other application you don't find in the gallery.
  3. Click Create.
  4. Review the app you’ve just created.
    4403310264337ScreenShot2021-06-30at91140AM.png
    Azure AD - All Applications Menu

Assignment Option

Assign Users and GroupsIn the properties Management tab, set User Assignment required? to NO.

Side-by-side with comments (Azure console and Solve settings)

Here is a side-by-side comparison of the values from Azure AD that must be entered into the Solve SAML settings and vice versa. The arrows indicate from where you can obtain the applicable string and to where it goes in the other application.
Azure AD Console                                                                     Solve SAML Settings
4403314638481ScreenShot2021-06-23at121542PM.png

Use Case Example - DUO

Prerequisites:

  • Must have a DUO account with the necessary permissions to Protect an Application.

What to do in on DUO

  1. In DUO, select Applications > Protect an application.
  2. Search for Generic Service Provider.
  3. Click Protect.
  4. In the Generic Service Provider - Single Sign-On page, enter the parameters from the Solve page as detailed in the procedure above and described in the illustration below.
  5. In the Solve page detailed in the procedure above, enter the parameters as described in this illustration below.


Side-by-side with comments (DUO and Solve settings)

DUO

Use Case Example - OKTA

Prerequisites:

  • Must have an Okta account with the necessary permissions to  Create App Integration.

Configuration:

  1.  Open Okta. Select Application and click Create App Integration.
    OKTA1
  2.  In the Create a new app integration dialog, select SAML 2.0. Click Next.
    OKTACreateAppInteg
  3. In the Create SAML Integration > 1 General Settings step, enter the App name field. Here we called the app Solve. The logo field is optional as are the App visibility options. Click Next.
    OKTACreateSAMLInt
  4.   In the Create SAML Integration > 2 Configure SAML step, enter the Single sign on URL. This value is taken from the Solve Settings user interface. It is the Endpoint/Assertion Login URL setting given by the Solve application to use in your identity provider software (per step 9 above). For OKTA, enter it here as the Single sign on URL.
    Select the Use this for Recipient URL and Destination URL option.
    OKTAConfigureSAML(2)
  5. In the Create SAML Integration > 3 Feedback step, select I'm an Okta customer adding an internal app.
    OKTACustomer(1)
  6.  Go to the Sign on tab for the new application you just created, and click the View Setup Instructions link. This enables you to access the x.509 certificate and other values from Okta that you must enter into the settings page in Solve.
    OKTASignOn(1)
  7.  In How to Configure SAML 2.0 for Solve Application: 
    1. Copy each of the values to enter into Solve settings as follows:
      Value from OktaCopy into Solve Settings
      Identity Provider Single Sign-On URLIdP Login URL
      Identity Provider IssuerEntity/Issuer ID 
    2.  Click Download certificate. Save it to a location accessible to when you open Solve settings so you can upload it there.
      OKTACertificate(1)
  8.  Open Solve and go to the Settings page to access the SAML configuration. Enter these values for Okta into Solve.


3rd Party Identity Provider Applications
We have provided these use case examples for your benefit but do not take responsibility for the screenshots, content and functionality for any of these 3rd party applications.







Was this article helpful?