Page tree
Skip to end of metadata
Go to start of metadata

The authentication integration service allows customers to authenticate their BMC Helix environments by standard external authentication systems via the Security Assertion Markup Language (SAML) protocol.


The following table describes when you might use specific authentication requests. You can choose to select this service during your initial onboarding project or at a later date as a Lifecycle Request.

Requestable offering nameWhen to use this offering type
SAML 2.0 SSO Federated Authentication RequestUse this request to authenticate your Helix environments by using your existing standard authentication systems.

Configure external authentication with one of the following customer-preferred authentication sources:

  • Security Assertion Markup Language (SAML) V2.0 using Active Directory Federation Services (ADFS) 2.0 or 3.0
  • SAML V2.0 using a third-party product (for example, Ping Identity, Shibboleth, and so on)

If you are upgrading or changing your identity provider, you must submit a change request to BMC SaaS Operations through your support portal. If you are using the portal, use the Request a Change option.


The development/tailoring, quality assurance, and production environments are all involved in the authentication process. Additional environments, if purchased, may be involved as well.

Required documentation

If you require BMC assistance for SAML-based authentication, you must submit your metadata file to BMC SaaS Operations via a support ticket. BMC will work with your technical contact to provide you with the service provider metadata that you must configure in your environment. This configuration requires active involvement with your authentication subject matter expert.

See Authentication options for a more detailed description of the available options.