Skip to main content

Chrome River (IdP-initiated) Integration Guide


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


1. Have a Chrome River account with SAML capabilities enabled

2. Create a New Realm for the Chrome River integration in the SecureAuth IdP Web Admin

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



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

For example, add the Chrome River ID directory field to the Email 2 Property if it is not already contained somewhere else

Global Aux Fields


2. Set Global Aux ID 1 to the Chrome River Company ID


Use the Global Aux Fields if the Company ID is a static value for all users; if it is unique to each user, then a different Profile Property must be utilized instead


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

Post Authentication


3. In the Post Authentication section, select SAML 2.0 (IdP Initiated) Assertion Page from the Authenticated User Redirect dropdown

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

User ID Mapping


5. Select the SecureAuth IdP Property that corresponds to the directory field that contains the Chrome River 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 Chrome River requires it, which the Service Provider (SP) provides

SAML Assertion / WS Federation


7. Set the SAML Consumer URL to<COMPANY ID>

8. Set the WSFed/SAML Issuer to a Unique Name that is shared with Chrome River

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

9. Set the SAML Recipient to<COMPANY ID>

10. Set the SAML Audience to

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

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

13. Select PasswordProtectedTransport from the AuthnContext Class dropdown


For steps 7 and 9, replace <COMPANY ID> with the actual Chrome River Company ID value


No configuration is required for the WSFed Reply To/SAML Target URL or SP Start URL fields


14. 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, then click Select Certificate and choose the preferred certificate

15. Provide the Domain in order to Download the Metadata File, which is sent to Chrome River

SAML Attributes / WS Federation


16. Set the Name of Attribute 1 to companyId

17. Select Global Aux ID 1 (or the attribute that contains the Chrome River Company ID) from the Value dropdown


Click Save once the configurations are 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.