Skip to main content
Sumo Logic

Integrate Sumo Logic with Bitium

  1. Last updated
  2. Save as PDF

Bitium is a cloud-based identity management provider that can be integrated with Sumo Logic’s SAML 2.0 API to allow users to log in to Sumo Logic using their Single Sign-On (SSO) credentials.SAML 2.0 API to allow users to log in to Sumo Logic using their Single Sign-On (SSO) credentials.

You can sign up for a free Bitium Trial account on the Bitum site. 

Create a Bitium SSO app to connect to Sumo Logic

  1. Sign into Bitium.
  2. From the Bitium menu, select Manage, and then select Manage Apps.
    Manage apps
  3. On the Apps page, select Add an App.
    Add an app
  4. Search for Sumo Logic to locate the Sumo Logic App for Bitium.
    Search for Sumo Logic
  5. On the App Install page, select Individual Account. Then under Single Sign-On, select SAML Authentication.
    Install
  6. Click Install App to move on to the next step.
  7. On the Install Success page, click Configure Single Sign-On.
    Install success
  8. For Single Sign-On Provider, select SAML Authentication.
    SAML Authentication
  9. The SAML configuration details for the App are displayed. For the Sumo Logic configuration, use the following parameters from this page:
    • EntityID
    • Login URL
    • LogOut URL
    • X.509 Certificate 
  10. Keep this page open to use these parameters in the next step, Configure SAML in Sumo Logic.

Configure SAML in Sumo Logic

  1. Log into Sumo Logic as an administrator.
  2. Go to Administration > Security > SAML.
  3. Click Configure, and configure the SAML settings.
    • Configuration Name. Type the name of the SSO policy (or another name used internally to describe the policy).
    • Debug Mode. Select this option if you'd like to view additional details when an error occurs. For more information, see Using SAML Debug Mode.
    • Issuer. Type the unique URL associated with your organization's SAML IdP. This is the Identity Provider Issuer from Step 12 in the previous section.
    • X.509 Certificate. Copy and paste your organization's X.509 certificate, which is used to verify signatures in SAML assertions. This is the Certificate, also from Step 12.
    • Attribute Mapping. Depending on your IdP, select:
      •  Use SAML subject, or
      • Use SAML Attribute and then type the email attribute name in the text box.
    • SP Initiated Login Configuration. Activate the check box. Then copy the unique hash from the Issuer URL and paste it into the Login Path field.
      Login Path. Enter a unique identifier for your organization. You can specify any alphanumeric string, provided that it is unique to your organization such as "yourcompanyname". The identifier is used to generate a unique URL for user login. For example, if you enter "yourcompanyname", the login URL for the HTTP redirect binding becomes:
      https://service.deployment.sumologic.com/sumo/saml/redirect/yourcompanyname
      And the login URL for the HTTP POST binding becomes: https://service.deployment.sumologic.com/sumo/saml/post/yourcompanyname

      where deployment is your specific deployment: us2|eu|au
    • Authn Request URL. Leave this blank. 
    • Disable Requested Authn Context. If you check this option, Sumo will not include the RequestedAuthnContext element of the SAML AuthnRequests it sends to your Idp. This option is useful if your IdP does not support the RequestedAuthnContext element.
    • Sign Authn Request. (Optional.) If you select this option, Sumo will send signed Authn requests to your IdP. When you click this option, a Sumo-provided X-509 certificate is displayed. You can configure your IDP with this certificate, to use to verify the signature of the Authn requests sent by Sumo. 
    • Roles Attribute: When you click this option, Roles Attribute field appears. Enter the SAML Attribute Name that is sent by the IdP as part of the assertion. For details, see Set SAML for Single Sign-On.
    • On Demand Provisioning. Select this option to have Sumo Logic automatically create accounts when a user first logs on. For more information, see Set Up SAML for Single Sign-on.
      • First Name
      • Last Name
      • On Demand Provisioning Roles. Add a role for all Bitium users, such as Administrator.
    • Logout Page: Select this option and enter a URL if you'd like to point all users to the URL after logging out of Sumo Logic. For more information, see Set Up SAML for Single Sign-On.
  4. Click Add.
  5. View the summary of the SAML configuration parameters. Leave this dialog open so that you can use these settings in Bitium.
    saml-config-details.png

Add Sumo Logic SAML Settings to SAML Settings to Bitium

  1. Go back to the Bitium SAML Configuration page.
  2. Within the SAML URL text box, enter the Authentication Request URL displayed in step 6 of the previous section.
    SAML URL
  3. Click Save Changes to complete the application install.
  4. Assign users as needed to the Sumo Logic App.
  5. You are now configured to login to Sumo Logic through Bitium.

 

Create multiple SAML configurations

You can create multiple SAML configurations in Sumo. To create an additional SAML configuration, click the plus (+) icon to create a new configuration. Enter the settings for the new configuration, as described the previous section.

saml-config-list.png

Require SAML for sign-in

After you create a SAML configuration, you can require users to sign in using SAML and prevent users from bypassing SAML with a username and password for login. Before you do so, follow the instructions in Check SAML Usage.

Check SAML Usage

If you intend to require Sumo users to sign-in using SAML, as described in the following section, Require SAML for sign-in, it is a best practice to first check whether some users are still logging in directly, instead of using SAML. You can run the following query to see, for a particular time range, whether users signed in using SAML or with their username and password:

_index=sumologic_audit action=login | count by class, sourceuser

The query results show, for each user that has accessed Sumo over the time range, the number of times they have logged in using SAML or by entering a Sumo username and password. In the class column:

  •  "SAML" indicates the user signed in using SAML.  
  •  "SESSION" indicates the user authenticated by entering a username and password.  

If the same user accessed Sumo using both methods (SAML and direct logon) during the time range, the query results will include a row for each method, showing how many times each method was used. 

saml-use-query.png

Require SAML for sign-in 

Click Require SAML Sign In to require users to sign in using SAML.

require-saml.png

Sumo automatically adds your account under Allow these users to sign in using passwords in addition to SAML as a whitelisted user as a preventative measure to ensure you’re still able to access Sumo if you run into issues.

Having only one user able to bypass SAML may not be convenient or practical if you have a global company or a large team. You can add additional whitelisted users by clicking the (+) icon by Allow these users to sign in using passwords in addition to SAML:

allow-users.png

We do not recommend denying all users password access to Sumo even if you want to enforce log in by SAML. If you attempt to delete your last remaining whitelisted user, you will receive a warning that this is not a recommended practice:

prevent-password-based-login.png

SAML lockdown limitations

There are two user account changes an admin cannot perform when the Require SAML Sign In option is selected:

  • You cannot change a user's login email address when SAML is locked down.
  • If a user's account has been locked as a result of too many failed login attempts, you cannot unlock the account while SAML is locked down.

To change a user's login email address or unlock a user account, you must toggle off the Require SAML Sign In option, make the update, and then turn Require SAML Sign In back on.