Enabling BMC Helix Single Sign-On for BMC Helix iPaaS, powered by Jitterbit


After your organization subscribes to BMC Helix iPaaS, powered by Jitterbit, BMC provisions and activates the system and provides information about how to access it. During system activation, the BMC SaaS Operations team configures BMC Helix Single Sign-On (BMC Helix SSO) in the BMC Helix SSO Admin Console to support seamless authentication of BMC users. For more information about your product activation, see BMC Helix iPaaS activation.

After that, as an administrator, you must enable the BMC Helix SSO authentication in BMC Helix iPaaS, powered by Jitterbit. The BMC SaaS Operations team can enable the single-sign on authentication for your organization if you have officially agreed upon this with BMC. 

Important

If your organization doesn't want to use BMC Helix SSO to access BMC Helix iPaaS, powered by Jitterbit, you are not required to enable the single-sign on authentication.

Related topics

BMC Helix iPaaS service

Orientation in BMC Helix SSO documentation

Before you begin

Make sure that the BMC Helix BMC SaaS Operations team has configured the single sign-on authentication for your organization in the BMC Helix SSO Admin Console.

Process for enabling BMC Helix SSO authentication for BMC Helix iPaaS, powered by Jitterbit

The following image shows the steps to enable the BMC Helix SSO authentication for BMC Helix IPaaS, powered by Jitterbit:

Process of enabling SSO authentication for JB.png

Task

Action

Reference

1

Request the BMC Helix Operations team to provide BMC Helix SSO configurations required to set up the single sign-on authentication in BMC Helix iPaaS, powered by Jitterbit.

As an administrator, you must enter these values later on while configuring the single sign-on authentication with OAuth 2.0 in BMC Helix iPaaS, powered by Jitterbit. 

2

Log in to BMC Helix iPaaS, powered by Jitterbit with Administrator credentials that you received in an activation email. 

Important: Only users that are assigned the Administrator role in BMC Helix iPaaS, powered by Jitterbit can enable the single sign-on authentication for their organization.

NA

3

Enable the single sign-on authentication in BMC Helix iPaaS, powered by Jitterbit. 

Important: From the Enable SSO field, select the OAuth 2.0 protocol. 
BMC Helix SSO uses the OpenID Connect authentication method to connect to BMC Helix iPaaS, powered by Jitterbit. OpenID Connect is built on top of the OAuth 2.0 protocol.

4

Set up the BMC Helix SSO authentication with OAuth 2.0 in BMC Helix iPaaS, powered by Jitterbit. Use the values that you obtained from the BMC Helix Operations team to configure the authentication. 

Important: From the OAuth Provider field, select BMC

5

Obtain the link to BMC Helix iPaaS, powered by Jitterbit and share it with the BMC Helix Operations team. The BMC Helix Operations team uses the link to make BMC Helix iPaaS, powered by Jitterbit available from BMC Helix Portal.

NA

BMC Helix SSO values for the single sign-on authentication

When you set up the single sign-on authentication with OAuth 2.0 in BMC Helix iPaaS, powered by Jitterbit, you must provide BMC Helix SSO authentication values for your organization. The BMC Helix SaaS Operations team configures these values for you in the BMC Helix SSO Admin Console, and therefore, can share them with you. Request the following BMC Helix SSO values from the BMC Helix SaaS Operations team:

Value

Description

Link 

Organization-specific link to identify your organization in BMC Helix iPaaS, powered by Jitterbit.

This link redirects users for the single sign-on authentication, without using the login page of BMC Helix iPaaS, powered by Jitterbit. The link is used in BMC Helix Portal as a tile for BMC Helix iPaaS, powered by Jitterbit in the Featured Application area or as a clickable link.

Redirect URL

Callback URL for the SSO client configured as a part of the OAuth 2.0 setup in BMC Helix SSO. The following two redirect URLs are provided in BMC Helix iPaaS, powered by Jitterbit:

  • Redirect URL for the Web Management Console (WMC) client. This URL has the following format: http://<zone-url-jitterbit>/jitterbit-cloud-mgmt-console/oauth
  • Redirect URL for the Studio client. This URL has the following format: http:///<zone-url-jitterbit>/jitterbit-cloud-mgmt-console/login/studio/callback

Important: These redirect URLs are provided by default in the Redirect URL fields that are associated with the corresponding clients. These URLs cannot be edited. However, to verify that the correct values are specified, request these redirect URLs from the BMC Helix SaaS Operations team.  

Client ID

Client identifier issued by BMC Helix SSO during the client registration process. Obtain this value for WMC and Studio clients. 

Client Secret

Client secret issued by BMC Helix SSO. Obtain this value for WMC and Studio clients. 

Subdomain

Subdomain of your organization.

BMC Helix SSO identifies tenants by using this subdomain. 

Custom User Info URL

URL to verify the email address of a BMC user.

This URL must be a Get request, and it also must use a token received from the OAuth token endpoint. 

Results

After you enable the BMC Helix SSO authentication in BMC Helix iPaaS, powered by Jitterbit, BMC users in your organization can access BMC Helix iPaaS, powered by Jitterbit by using their credentials. For more information about accessing BMC Helix iPaaS, powered by Jitterbit with BMC Helix SSO, see Accessing-BMC-Helix-iPaaS-powered-by-Jitterbit-with-BMC-Helix-Single-Sign-On.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*