Skip to end of metadata
Go to start of metadata


Passwords for Jitterbit Harmony are controlled within the Organizations page of the Management Console. The password control features are set for each individual organization separately. Only an Administrator for the organization has access to revise the password controls.

NOTE: Password controls for organizations using single sign-on are managed through the Identity Provider.

Manage Password Controls

Log in to the Harmony Portal and choose Management Console. Then click the orange hamburger menu in the top left and from the menu select Organizations.

On the far right of each row of the organizations table are the available Actions for Admins:

Choose Edit Organization to update basic information about your organization (name, address, time zone):

Choose Edit Organization Policies to enable/disable or specify the following settings. Each configurable field or action is explained below.

Settings that do not apply to organizations using SSO are noted. Members who are on the Bypass SSO list will be subject to the org policies for any other non-SSO-enabled orgs of which they are a member.

  • Password Require special character(s): Require at least one special character per Harmony password for each registered user within the organization. This setting does not apply to SSO orgs.
  • User password expires in: Require the organization's registered users to change passwords every X number of days. This setting does not apply to SSO orgs.
  • Disable user accounts in: Disable any account registering no activity within X number of days. This setting applies to both Harmony and SSO orgs.
  • Password history: Require users with forgotten password to identify the last X number of used passwords. This setting does not apply to SSO orgs.
  • Two-Factor Authentication (TFA): Require two-factor authentication (TFA). All of the organization's members will be required to enter a verification code sent by Jitterbit (in addition to their username and password) when they sign in. They will be required to reverify their devices every X number of days. This setting does not apply to SSO orgs.
  • TFA on each login: Require two-factor authentication on every login as opposed to every X number of days. This setting does not apply to SSO orgs.
  • Enable remote Agent configuration: Enable remote agent configuration (via the Management Console from the Agents > Agent Groups page).
  • Member's domains: Restrict access to the following domains. Separate multiple domains using commas or semicolons.
  • Enable SSO: Enable SSO for all members of the org, except for those included under Bypass SSO. More information about SSO options is provided under Enable SSO.

    NOTE: Configuring and enabling SSO is a two-step process:

    1. Configure SSO: First, select SAML 2.0 or OAuth 2.0 to open a new screen to configure SSO. Click Save within this popout to save the configuration but not yet enable SSO. 
    2. Enable SSO: Next, make sure the appropriate configuration for SAML 2.0 or OAuth 2.0 is selected and click Save within the Edit Organization Policies screen to enable SSO using your configured settings.
  • Bypass SSO: Bypass the SSO settings for users added within the popout screen. The Bypass SSO list applies only when SSO is enabled; however, you can still manage your Bypass SSO list when SSO is disabled, for example to prepare for enabling SSO. More information about exempting users from SSO is provided under Bypass SSO.

    NOTE: When you make changes to the Bypass SSO list and click Save within this popout, the changes will be saved regardless of if you Save or Cancel out of the Edit Organization Policies screen.
  • Enable Whitelist IP Range: Require the user to log in only from the specified IP range (note, this applies to all client systems, websites, and Studio).
  • Save/Cancel: Choose Save to save any changes to the organization policies, or Cancel to close without saving. The Save button will be disabled unless changes have been made, with the exception of the Bypass SSO list (see note above).

On This Page

Last updated:  Apr 10, 2019