Vulcan Cyber

The Vulcan Cyber ExposureOS Platform supports ALL SAML2-based SSO solutions and provides instruction for setting up SSO on <a href="https://help.vulcancyber.com/en/articles/6336509-configure-single-sign-on-authentication-sso">Okta, OneLogin, and AzureAD platforms</a>.

To set up your own SSO SAML2-based with the Vulcan Cyber ExposureOS SSO solution, you'll need to configure the SAML 2.0 integration between the two systems. Here's a general overview of the steps involved that are relevant to any SAML 2.0 tool:

Go to your SSO solution and create a new SAML-2 application.

In the application's setting, make sure to:

1. Give the application an indicative name, such as "Vulcan SSO".
2. Insert the following Vulcan Cyber ExposureOS identifier in the relevant fields (Entity ID, Reply URL, and any other URL identifier). All URLs are identical, with the format: ​<code>https://myinstanceID.vulcancyber.com/api/saml2_auth/acs/</code>
 Make sure to replace "myinstanceID" with your own domain/environment name in the Vulcan Cyber ExposureOS.
3. Add the following statements and map them to the relevant values on your end (case sensitive):
 - <code>givenname</code> (user first name field on your end)
 - <code>surname</code> (user last name on your end)
 - <code>name</code> (user email address on your end)
 - For reference, we recommend looking into the following SSO attributes mapping configurations of the following vendors:
 - <a href="https://help.vulcancyber.com/en/articles/3277407-how-to-configure-okta-single-sign-on-with-vulcan">Okta</a>
 - <a href="https://help.vulcancyber.com/en/articles/4681233-how-to-configure-onelogin-single-sign-on-with-vulcan">OneLogin</a>
 - <a href="https://help.vulcancyber.com/en/articles/3303975-how-to-configure-azure-ad-single-sign-on-with-vulcan">Azure AD</a>
4. Generate the XML metadata file.

Go to the Vulcan Cyber ExposureOS platform &gt; Settings &gt; Authentication.

Follow the instructions on the SSO configuration page, starting from Step 2.

Test the SSO integration. Once the configuration is complete, perform thorough testing to ensure that the SSO integration is functioning as expected. This involves logging in to Vulcan Cyber's ExposureOS SSO using your SSO tool as the identity provider and verifying that the user is successfully authenticated.

1. Go to your SSO solution and create a new SAML-2 application.
2. In the application's setting, make sure to:
 1. Give the application an indicative name, such as "Vulcan SSO".
 2. Insert the following Vulcan Cyber ExposureOS identifier in the relevant fields (Entity ID, Reply URL, and any other URL identifier). All URLs are identical, with the format: ​<code>https://myinstanceID.vulcancyber.com/api/saml2_auth/acs/</code>
 Make sure to replace "myinstanceID" with your own domain/environment name in the Vulcan Cyber ExposureOS.
 3. Add the following statements and map them to the relevant values on your end (case sensitive):
 - <code>givenname</code> (user first name field on your end)
 - <code>surname</code> (user last name on your end)
 - <code>name</code> (user email address on your end)
 - For reference, we recommend looking into the following SSO attributes mapping configurations of the following vendors:
 - <a href="https://help.vulcancyber.com/en/articles/3277407-how-to-configure-okta-single-sign-on-with-vulcan">Okta</a>
 - <a href="https://help.vulcancyber.com/en/articles/4681233-how-to-configure-onelogin-single-sign-on-with-vulcan">OneLogin</a>
 - <a href="https://help.vulcancyber.com/en/articles/3303975-how-to-configure-azure-ad-single-sign-on-with-vulcan">Azure AD</a>
 4. Generate the XML metadata file. 
3. Go to the Vulcan Cyber ExposureOS platform &gt; Settings &gt; Authentication.
4. Follow the instructions on the SSO configuration page, starting from Step 2. 
 
 
 
5. Test the SSO integration. Once the configuration is complete, perform thorough testing to ensure that the SSO integration is functioning as expected. This involves logging in to Vulcan Cyber's ExposureOS SSO using your SSO tool as the identity provider and verifying that the user is successfully authenticated.