CloudSploit supports SAML login for all paid users. To enable SAML, support will request several pieces of information from you. We will then enable SAML for a single user within your account so that no one loses access, allow you to test the configuration end-to-end, and then enable it for all of your users.
CloudSploit supports nearly all SAML 2.0-compliant identity providers. These include: Okta, Auth0, ADFS, OneLogin, and numerous others. The provider must be capable of generating an XML metadata file, or providing an endpoint at which the XML metadata can be accessed.
Create a SAML Application
To begin enabling SAML, you must first create a new application for CloudSploit in your SAML provider. This differs by provider, but most providers will require the following information:
|Application Callback URL||https://cloudsploit.auth.us-east-1.amazoncognito.com/saml2/idpresponse|
|Allowed Callback URLs||https://cloudsploit.auth.us-east-1.amazoncognito.com/saml2/idpresponse|
|Signin / Signout URL||https://cloud.aquasec.com/sso|
Providing a Metadata File
After you have created your SAML application, you will need to provide your application information to CloudSploit. This can either be in the form of an exported XML metadata file, or a link to an XML metadata endpoint. You can validate your XML file using an online SAML XML validator.
Initiating the SAML Setup
Once you have collected the above information and configured your application, please contact CloudSploit Support and provide the following information:
- Your XML file or XML metadata endpoint
- The domains you'd like to allow to authenticate with your account. CloudSploit can support an unlimited number of domains.
- Whether you would like to enforce SAML login for all users in your account (if yes, existing usernames/passwords will no longer work and SAML will be enforced for all new and existing users).
- Whether you would like to enable just-in-time provisioning of user accounts (if yes, new users will be added to the "Default" groups).
- Which user (email address) you'd like to use to test the configuration before enabling it globally.
Once support confirms receipt of the above, we will enable SAML for your account, but only apply it to the user you specify. This is done to prevent incorrect SAML configurations from locking out all other users in your account.
Support will then ask you to confirm the workflow by testing a SAML signin. If everything succeeds, we will then enable it for all other users.
Azure Active Directory
For Azure AD, please use the following settings: