Administrative Utilities → Authentication → Configuring Authentication Settings
On-demand administrators can enable authentication for end users via a third-party identity provider using SAML2. This means an external entity such as Tivoli, SiteMinder, or Oracle Identity Manager can perform user authentication for SBM and send authenticated user credentials back to SBM to log the user in to the system.
SAML2 requires a trust relationship between the external identity provider and the service provider (SBM) via an exchange of metadata between the two entities. In SBM, you retrieve the service provider metadata (which includes a unique entity ID) and you use it to register SBM with your identity provider. You will then obtain metadata from the identity provider and enter it into SBM to establish the trust.
The following steps describe how to perform a typical metadata exchange.
Copyright © 2007–2018 Serena Software, Inc., a Micro Focus company. All rights reserved.