Skip to main content

Fuze (IdP-initiated) Integration Guide


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


1. Have a Fuze account with SAML capabilities enabled

2. Create a New Realm for the Fuze 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 attribute that contains the user's First Name to the SecureAuth IdP First Name Property

2. Map the directory field that contains the user's Last Name to the SecureAuth IdP Last Name Property

3. Map the directory field that contains the user's Email Address to the SecureAuth IdP Email 1 Property

4. Map the directory field that contains the user's Fuze ID to the SecureAuth IdP Property

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


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

Post Authentication


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

6. 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


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

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

Select a different option if Fuze requires it, which the Service Provider (SP) provides

SAML Assertion / WS Federation


9. Set the SAML Consumer URL to<DISCOVERY KEY>

10. Set the WSFed/SAML Issuer to a Unique Name that is shared with Fuze

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

11. Set the SAML Recipient to<DISCOVERY KEY>

12. Set the SAML Audience to

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

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

15. Select PasswordProtectedTransport from the AuthnContext Class dropdown


For steps 9 and 11, replace <DISCOVERY KEY> with the actual Discovery Key value, provided by a Fuze administrator


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


16. 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

17. Provide the Domain in order to Download the Metadata File, which is sent to Fuze

SAML Attributes / WS Federation


18. Set the Name of Attribute 1 to firstName

19. Select First Name from the Value dropdown (step 1 Property mapping)

20. Set the Name of Attribute 2 to lastName

21. Select Last Name from the Value dropdown (step 2 Property mapping)

22. Set the Name of Attribute 3 to email

23. Select Email 1 from the Value dropdown (step 3 Property mapping)


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.