Onboarding your organization to SC//Nexus

Onboarding your organization to SC//Nexus

This topic is for the administrator who sets up SC//Nexus™ access for your organization. It gives an overview of the setup from start to finish: what you configure in your own identity provider, what you send to Scale Computing, and what Scale Computing does with it. Each step links to the detailed procedure.

Setup is done once for each organization. After setup, your members sign in through your identity provider as described in Signing in to SC//Nexus.

How the work is divided

SC//Nexus federates with your identity provider using SAML 2.0. Setting up federation means configuring both sides of the connection, and the work is split between you and Scale Computing.

Who What they do
You Create a SAML application for SC//Nexus in your identity provider, assign your users to it, and send the resulting identity provider details to Scale Computing.
Scale Computing Create your organization in SC//Nexus, map it to the Scale Computing products you're entitled to, and attach your identity provider to the organization.

Your identity provider handles authentication, including credentials, multi-factor authentication, and any conditional access policies you enforce. SC//Nexus decides which Scale Computing products each member can open, based on what your organization is entitled to.

Before you start

You need the following:

  • Administrator access to your identity provider. You need permission to create a SAML application and assign users to it.
  • The email addresses of the people who need access. Each member's SC//Nexus account is identified by email address. That address must match the email address your identity provider sends for the user when they sign in. It must also match the email address on the user's account in each Scale Computing product, such as SC//AcuVigil™ or SC//Reliant™ Platform Manager. Capitalization differences are the most common cause of a mismatch.

Step 1: Get the SC//Nexus service provider details

Your identity provider needs the SC//Nexus service provider details to set up the connection. SC//Nexus publishes them in three forms: a metadata URL, a metadata XML file, and individual values for manual entry. Use whichever form your identity provider accepts.

The SC//Nexus metadata URL is https://nexus.scalecomputing.com/api/v1/saml/metadata.

For the individual values and how to use each form, see Configuring an identity provider that supports SAML 2.0.

Step 2: Create a SAML application in your identity provider

Create a SAML 2.0 application for SC//Nexus in your identity provider, using the service provider details from Step 1. Whichever identity provider you use, the application must meet the following requirements:

  • The Assertion Consumer Service (ACS) URL is set to https://nexus.scalecomputing.com/sso/api/oauth/saml.
  • The identity provider signs the assertion. SC//Nexus requires a signed assertion.
  • The NameID is the user's email address. It must match the email address on the user's SC//Nexus account.
  • The identity provider doesn't require signed authentication requests. SC//Nexus doesn't sign its requests.
  • Single logout is left blank. SC//Nexus doesn't support single logout.

For the procedure for your identity provider, see one of the following topics:

If you use another identity provider, follow its documentation for adding a custom SAML 2.0 application, and contact Scale Computing Support if you need assistance.

Step 3: Assign users to the application

In your identity provider, assign the SAML application to the users or groups who need access to SC//Nexus. Users who aren't assigned to the application can't sign in to SC//Nexus, even if they have an SC//Nexus account.

Step 4: Send your identity provider details to Scale Computing

Once the application is set up, your identity provider generates its own SAML metadata. Send Scale Computing the following:

Item Description
Identity provider name The name that appears on the Sign in with <identity_provider> button that members see after they enter their email address. For example, if the name is Entra, the button reads Sign in with Entra. Choose a name your members will recognize as your company's sign-in.
SAML metadata URL or SAML metadata (XML) The metadata your identity provider generated for the SC//Nexus application. Send one or the other, not both. The SAML metadata URL is the URL your identity provider publishes its metadata at, for example https://your-idp.example.com/saml/metadata. The SAML metadata (XML) is the metadata XML file, which you can usually download from your identity provider's admin console.
User email addresses The email addresses of the people who need SC//Nexus accounts.

Send these to your Scale Computing account manager or Support. The metadata contains no secrets, but send it through a channel you trust so it can't be altered on the way.

Step 5: Scale Computing configures your organization

Scale Computing uses the details you sent to complete the SC//Nexus side of the setup:

  1. Creates your organization in SC//Nexus.
  2. Maps your organization to the Scale Computing products you're entitled to, such as SC//AcuVigil or SC//Reliant Platform Manager.
  3. Attaches your identity provider to your organization.
  4. Creates SC//Nexus accounts for your members.

Scale Computing tells you when your organization is ready.

Step 6: Test sign-in

Before you announce SC//Nexus to your members, sign in yourself to confirm the setup:

  1. Go to https://nexus.scalecomputing.com/ and enter your email address. SC//Nexus confirms the address with Signing in as followed by your email address. If the address is wrong, choose Use a different email.
  2. Choose Sign in with <identity_provider>, where <identity_provider> is the identity provider name you sent in Step 4, and complete authentication at your identity provider.
  3. Confirm that the Your applications page opens and lists the products your organization is entitled to.
  4. Choose Access now for each product and confirm that it opens.

If sign-in fails, check the following:

Symptom Likely cause
Your identity provider reports a reply URL or ACS URL mismatch, for example Microsoft Entra error AADSTS50011. The ACS URL in your SAML application isn't https://nexus.scalecomputing.com/sso/api/oauth/saml.
SC//Nexus asks for a password instead of offering your identity provider. SC//Nexus didn't find an account for the email address you entered. Check for a typo, and make sure you entered the address on your SC//Nexus account rather than an alias.
Your identity provider authenticates you, but SC//Nexus rejects the sign-in. The email address your identity provider sends doesn't match your SC//Nexus account, or your user isn't assigned to the SAML application.
SC//Nexus opens, but a product fails to open from Your applications. The email address on your account in that product doesn't match your SC//Nexus email address.

For more about the member sign-in experience, see Signing in to SC//Nexus.

Related topics