Fuze (IdP-initiated) Integration Guide
Introduction
Use this guide to enable Multi-Factor Authentication and Single Sign-on (SSO) access via SAML to Fuze.
Prerequisites
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
Data
 |
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
Warning
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 https://www.fuzemeeting.com/fuze/saml_verify/<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 https://www.fuzemeeting.com/fuze/saml_verify/<DISCOVERY KEY>
12. Set the SAML Audience to www.fuzemeeting.com
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
Note
For steps 9 and 11, replace <DISCOVERY KEY> with the actual Discovery Key value, provided by a Fuze administrator
Note
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)
Warning
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.
 |
In the Forms Authentication section, set the following:
Require SSL
If the SSL is required to view the token, set to True.
Cookieless
Indicate whether SecureAuth IdP will deliver the token in a cookie to the user's browser or device:
UseCookies – Always deliver a cookie
UseUri – Do not deliver a cookie, deliver the token in a query string
AutoDetect – Deliver a cookie if the user's settings allow it.
UseDeviceProfile – Deliver a cookie if the browser settings allow it, regardless of the user's settings
Sliding Expiration
For the cookie to remain valid as long as the user is interacting with the page, set to True.
Timeout
Set the length of time in minutes the cookie is valid.
In the Machine Key section, set the following:
Validation
If the default value does not match your organization's requirements, choose another value.
Decryption
If the default value does not match your organization's requirements, choose another value.
In the Authentication Cookies section, set the following:
Persistent
Set one of the following values:
True - Expires after Timeout – Allow the cookie to be persistent
False - Session Cookie – Allow the cookie to be valid as long as the session is open, and expires when the browser is closed or the session expires
Save your changes.
Note
To configure this realm for SSO, refer to SecureAuth IdP Single Sign-on Configuration
Note
To configure this realm for Windows Desktop SSO, refer to Windows desktop SSO configuration