Skip to main content
Feedback

Configuration SAML

Overview

This interface is dedicated to configuring Security Assertion Markup Language (SAML) settings. The purpose of SAML is to enable secure, single sign-on (SSO) capabilities across different domains. This allows an administrator to manage the identity provider (IdP) configuration required to establish a trust relationship between the service provider (the application) and the IdP. SAML is a login standard that helps users access applications based on sessions in another context. It’s a single sign-on (SSO) login method offering more secure authentication than usernames and passwords.

Administration Portal - Configuration - SAML

SAML Configuration

OptionDescription
DisabledIndicates if the SAML configuration is currently active.
Login PageA URL that is the entry point for users to initiate a login process via their IdP.
IDP Entity IDA unique identifier for the IdP within the SAML configuration.
Certificatea digital certificate in PEM format. This is crucial for establishing a secure connection, as it contains the public key that will be used to verify SAML assertions from the IdP.
Attribute Display NameName of the user attribute that holds the display name.
Attribute EmailName of the user attribute that holds the email address.
Attribute RoleName of the user attribute that holds the user's role. This allows the SAML IdP to assign user roles.
Attribute Role Admin ValueAllows the specification of a value that, if received in the role attribute, grants administrative rights to the user.
SP Entity IDProvided by Boomi and cannot be edited. The service provider's unique identifier where the IdP should send its response after authenticating a user.
Login Response UrlProvided by Boomi and cannot be edited. The service provider's endpoint where the IdP should send its response after authenticating a user. These endpoints are typically where the application expects to receive SAML assertions.

Advanced Options

The advanced options allow users to use the SAML configuration on API Control Plane instead of the SSO configuration from the Boomi Platform. This configuration allows you to use the Login with Boomi Platform option on the API Control Plane Developer Portal login page.

Prerequisites

  • The user who is logging in must be a Boomi Platform user with access to the API Control Plane.
  • The Federation ID must be populated for the user in User Management, and the Federation ID must match what the SAML IDP will return.

Administration Portal - Configuration - Advanced SAML

OptionDescription
Use for Boomi Platform loginIf enabled, Boomi platform users can also log in using this SAML configuration.
Federation ID from Name IDIf enabled, the federation ID is extracted from the Name ID of the SAML assertion.
Authentication ContextSpecifies the authentication context that is requested from the SAML IdP during the authentication process. Password Protected Transport - requests that the user is authenticated using a password over a secure (TLS/HTTPS) connection.Unspecified - Allows the IdP to choose the authentication method without asking for a specific assurance level. None - Does not request any specific authentication context. The IdP uses its default authentication.
Authentication Context ComparisonDefines how the requested authentication context should be compared to the contexts supported by the SAML IdP. Exact - Requires the IdP to use an authentication context that exactly matches the one requested. Minimum - Allows the IdP to use the requested context or any stronger authentication context, but not weaker ones. None - Does not require any specific comparison. The IdP can use its default way of evaluating the authentication context.
Name ID PolicySpecifies the format of the name ID to use in SAML assertions. Unspecified - No specific format for the Name ID is required. The IdP can use any supported format. Transient - Requests a temporary, session-specific Name ID that changes each time and cannot be linked across sessions. None - A Name ID format is not requested or required in the SAML assertion.
On this Page