Send Docs Feedback

Note: Most user interface tasks can be performed in Edge Classic or the New Edge experience. For an overview, getting started topics, and release notes specific to the New Edge experience, see the docs.

Using SAML authentication

SAML authentication is not supported on the Developer Services portal for Private Cloud at this time.

The Security Assertion Markup Language (SAML) specification defines formats and protocols that enable applications to exchange XML-formatted information for authentication and authorization. Administrators of organizations that have been configured for single sign-on (SSO) can configure the developer portal to use SAML authentication. 

The Developer Services portal acts as a client for Edge. That means the portal does not function as a stand-alone system. Instead, much of the information used by the portal is actually stored on Edge. When necessary, the portal makes a request to retrieve information from Edge or to send information to Edge.

By default the connection between the portal and Edge uses Basic Auth. If you enable SAML authentication on Edge, then the portal must be updated to use SAML authentication to connect to Edge. With SAML enabled, access to the Edge UI and Edge management API still uses OAuth2 access tokens. However, now you can generate these tokens from SAML assertions returned by an identity provider.

For complete details, see Configure the Developer Services portal for SAML.

After you enable SAML on the portal, the portal connects to Edge by using SAML authentication. However, portal developers, meaning the developers building apps by using your APIs, continue to log in to the portal using Basic Auth as defined by the portal.

 

Help or comments?