Blue Jeans (IdP-initiated) Integration Guide
Introduction
Use this guide to enable SecureAuth IdP-initiated Multi-Factor Authentication and Single Sign-on (SSO) access via SAML to Blue Jeans Video Conferencing Service.
For Service Provider (SP)-initiated integration, refer to Blue Jeans (SP-initiated) Integration Guide.
Prerequisites
1. Have an Enterprise Tier Blue Jeans account
2. Ensure that SAML SSO is enabled through an administrator account
3. Create a New Realm in the SecureAuth IdP Web Admin for the Blue Jeans integration
4. 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 end-user's email address attribute (e.g. mail) to a SecureAuth IdP Profile Property (e.g. Email 1)
Warning
Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes
Post Authentication
 |
2. In the Post Authentication section, select SAML 2.0 (IdP Initiated) Assertion Page from theAuthenticated User Redirect dropdown
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)
User ID Mapping
 |
4. Select Authenticated User ID from the User ID Mapping dropdown (default)
5. Select urn:oasis:names:tc:SAML:2.0:nameid-format:persistent from the Name ID Format dropdown
6. Select False from the Encode to Base64 dropdown
SAML Assertion / WS Federation
 |
7. Set the WSFed Reply To/SAML Target URL to https://bluejeans.com/sso/saml2/?RelayState=<Relay State Value>
8. Set the SAML Consumer URL to https://bluejeans.com/sso/saml2/?RelayState=<Relay State Value>
Note
The Relay State Value(required for steps 7 - 8) is generated in the Blue Jeans Configuration Steps (below) and is unique per integration
9. Set the SAML Recipient to https://bluejeans.com/sso/SAML2/
10. Set the SAML Audience to http://samlsp.bluejeans.com
11. Select True from the Sign SAML Assertion dropdown
 |
12. 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
13. Download the Assertion Signing Certificate, which is used in the Blue Jeans Configuration Steps
SAML Attributes / WS Federation
 |
14. Set the Name of Attribute 1 to Email
15. Select Email 1 (or an alternate SecureAuth IdP Profile Property to which the end-user's email address is mapped) from the Value dropdown
16. Set the Name of Attribute 2 to userid
17. Select Authenticated User ID from the Value dropdown
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.
 |
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
Blue Jeans Configuration Steps
 |
1. Log into the Blue Jeans administrative console
2. Select Admin from the top menu, then Group Settings, and open the Security tab
3. Select SAML Single Sign On from the Authentication Options section
4. Check Enable automatic provisioning to link accounts to automatically be created after successful SecureAuth IdP authentication (optional)
5. Click Choose File in the Certificate Path section, and select the Assertion Signing Certificate from the SecureAuth IdP Web Admin (step 13)
6. Set the Login URL to the Fully Qualified Domain Name (FQDN) of the SecureAuth IdP appliance, followed by the Blue Jeans-integrated realm, e.g. https://secureauth.company.com/secureauth2/
7. Set the Password Change URL to the SecureAuth IdP Password Reset Realm to enable easy password reset (optional)
8. Set the Logout URL to any URL to where end-users are redirected upon logging out (optional)
9. Set the User Id field to userid
10. Set the Email field to Email
11. Click Save Changes
Note
*Relay State: Once the configuration is saved, the unique Relay State Value is generated and must be copied and pasted into the Blue Jeans-integrated realm in the SecureAuth IdP Web Admin (steps 7 - 8)
Troubleshooting / Common Issues
If a validation error occurs when importing the Assertion Signing Certificate to Blue Jeans, then export the public key directly from the Windows Certificate Store instead.