SAML and Console
IBM Aspera Console supports Security Assertion Markup Language (SAML) 2.0, an XML-based standard that allows secure web domains to exchange user authentication and authorization data. With the SAML model, you can configure Console as a SAML online service provider (SP) that contacts a separate online identity provider (IdP) to authenticate users. Authenticated users can then use Console to access secure content.
With SAML enabled, Console redirects a user to the IdP sign-on URL. The user signs in with the IdP and the IdP sends a SAML assertion back to Console. When a SAML user logs in to Console for the first time, Console automatically creates a new user account based on the information provided by the SAML response. Any changes subsequently made to the account on the DS server are not automatically picked up by Console. For more information about user provisioning for SAML users, see User Accounts Provisioned by Just-In-Time (JIT) Provisioning.
IdP Requirements
To use SAML with Console, you must already have an identity provider (IdP) that meets the following requirements:
- Supports SAML 2.0
- Able to use an HTTP POST Binding.
- Able to connect to the same directory service that Console uses.
- Not configured to use pseudonyms.
- Can return assertions to Console that include the entire contents of the signing certificate.
- If prompted, set to sign the SAML response. (Signing the SAML assertion is optional.)
Configure the SAML IdP
Before configuring SAML in Console, make sure you configure your IdP to send a correct SAML response to Console. For more information, see Configuring Your Identity Provider (IdP).
SAML and Directory Services
Console supports the use of both SAML and directory services. If you configure both services to Console, ensure the services use different Active Directory domains. Aspera advises against configuring LDAP directly to Console if the SAML IdP acts as a frontend for the same Active Directory domain.Bypassing the Default SAML IdP
Console provides a mechanism for users to bypass the SAML redirect and log in using a local username and password. This feature allows admins to correct server settings, including a misconfigured SAML setup, without logging in through SAML.
To bypass the SAML login, add login?local=true to the end of the login URL. For example:https://IP/aspera/console/login?local=true