Skip to main content

Remedyforce (IdP-initiated) Integration Guide

Introduction

Use this guide to enable Multi-Factor Authentication and Single Sign-on (SSO) access via SAML to Remedyforce.

Prerequisites

1. Have a Remedyforce account

2. Create a New Realm for the Remedyforce integration

3. Configure the following tabs in the Web Admin before configuring the Post Authentication tab:

  • Overview – the description of the realm and SMTP connections must be defined

  • Data – an enterprise directory must be integrated with SecureAuth IdP

  • Workflow – the way in which users will access this application must be defined

  • Multi-Factor Methods – the Multi-Factor Authentication methods that will be used to access this page (if any) must be defined

SecureAuth IdP Configuration Steps

Data

44832223.png

1. In the Profile Fields section, map the directory field that contains the user's Remedyforce ID to the SecureAuth IdP Property

For example, add the Remedyforce ID Field to the Email 2 Property if it is not already contained somewhere else

Warning

Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes

Post Authentication

44831397.png

2. Select SAML 2.0 (IdP Initiated) Assertion Page from the Authenticated User Redirect dropdown in the Post Authentication tab in the Web Admin

3. An unalterable URL will be auto-populated in the Redirect To field, which will append to the domain name and realm number in the address bar (Authorized/SAML20IdPInit.aspx)

4. A customized post authentication page can be uploaded, but it is not required

User ID Mapping

60564688.png

5. Select the SecureAuth IdP Property that corresponds to the directory field that contains the Remedyforce ID (Email 2)

6. Select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified from the Name ID Format dropdown (default)

Select a different option if Remedyforce requires it, which the SP will provide

7. Select False from the Encode to Base64 dropdown

SAML Assertion / WS Federation

44832218.png

8. Set the WSFed Reply To/SAML Target URL to https://saml.salesforce.com

9. Set the Consumer URL to https://login.salesforce.com, and include the ID number, which can be obtained from Remedyforce (e.g. https://login.salesforce.com?ID=XXXXXXXXXXX)

Retrieve this URL from the Remedyforce Login URL field after saving the SAML settings

10. Set the WSFed/SAML Issuer to a Unique Name that will be shared with Remedyforce

The WSFed/SAML Issuer must match exactly on the SecureAuth IdP side and the Remedyforce side

11. Set the SAML Recipient tohttps://login.salesforce.com, and include the ID number, which can be obtained from Remedyforce (e.g. https://login.salesforce.com?ID=XXXXXXXXXXX)

Retrieve this URL from the Remedyforce Login URL field after saving the SAML settings

12. Set the SAML Audience to https://saml.salesforce.com

13. Set the SAML Offset Minutes to make up for time differences between devices

14. Set the SAML Valid Hours to limit for how long the SAML assertion is valid

Note

No configuration is required for the SP Start URL field

70489017.png

15. Leave the Signing Cert Serial Number as the default value, unless there is a third-party certificate being used for the SAML assertion

If using a third-party certificate, click Select Certificate and choose the appropriate certificate

16. Provide the Domain in order to Download the Metadata File to send to Remedyforce (if required)

Warning

Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changes

Forms Auth / SSO Token

Optionally, in the Forms Auth / SSO Token section, click the View and Configure FormsAuth keys/SSO token link to configure the token/cookie settings and configure this realm for SSO.

44833086.png

Remedyforce Configuration Steps

44832224.jpeg

1. Log into the Remedyforce Control Panel (https://login.salesforce.com)

2. Click Setup, expand Security Controls, and click Single Sign-On Settings

3. Click New

4. Set the Issuer value to the same UniqueName as provided in the SecureAuth IdP Web Admin (step 10)

5. Choose the certificate that is used in the SecureAuth IdP Web Admin (step 15) by clicking Choose File

6. Select Assertion contains User's salesforce.com username from the SAML Identity Type options

7. Select Identity is in the NameIdentifier element of the Subject statement from the SAML Identity Location options

8. Set the Identity Provider Login URL to the Fully Qualified Domain Name (FQDN) of the SecureAuth IdP appliance followed by the realm number of the Salesforce integration and secureauth.aspx

e.g. https://secureauth.company.com/secureauth1/secureauth.aspx

9. Set the Identity Provider Logout URL to the URL to where end-users will be redirected upon logging out of Salesforce

10. Mark HTTP Redirect from the Service Provider Initiated Request Binding options

11. Set the Entity ID to https://saml.salesforce.com

12. Click Save and review the configurations

In this section: