OKTA SSO Integration

StatusCast allows you to utilize the SSO feature built into Okta so that you’re administrators and users don’t need to manage multiple passwords.

Okta Settings

First need to login to Okta with an administrative user and navigate to the Applications section. Click the Create App Integration button.

If prompted select SAML 2.0 and click Next.

The general settings for this new application are unique to your Okta account and do not effect the integration; choose a name that you can simply identify later on. Select Next once you’ve filled out the form.

Enter the following for your SAML Settings:

Set the Name ID Format to EmailAddress and the Application username to Email.

Select Next once you’ve filled out the SAML settings.

Lastly Okta will prompt you if you’re a customer or partner; select the customer option, the rest of the form is optional. To complete the Okta Application setup select Finish.

You should now be viewing the application in your Okta account. Here you can grant users and groups access to this application within your account. To complete the integration you’ll have to activate it within StatusCast but before you log out of Okta you’ll need two bits of info from the newly created application.

Navigate to the Sign On tab in the application, and you should see the notice that “SAML 2.0 is not configured until you complete the setup instructions.” Click the View Setup Instructions button which will open a new tab/window. Keep this open as you will need to copy a few things into StatusCast.

Statuscast Settings

In a new tab or window log into your StatusCast admin portal. Navigate to the Integrations section by clicking Settings > Integrations. Under the SSO card select the Install option. (https://[yourapp].status.page/admin/integrations/sso)

349

SSO Integration

Click Add SSO Configuration

Add SSO

To complete the integration select the role you want to assign users first. You can assign user roles to allow permissions to view or access specific component data. You should go through this process for each role you will be using SSO for authentication in StatusCast. You may set up more than one provider per role.

SSO Settings

Each Integration set up must have a unique path and Certificate even if the SSO provider is the same for varying roles.

  1. Select the User Role
  2. Select OKTA your SSO Provider Type
  3. Fill in the details for the integration. See the chart below for details
  4. Be sure to Save your configuration using the orange button at the top when completed.
  5. Continue adding additional Configurations as needed
LabelDescription
NameGive this set-up a name so you can distinguish it if you need to make a change
Login PathAll SSO logins use your page url /login/[myloginpath]. This value is the part or your URL after the /login/ . This is the endpoint for the users allowing them to login using this SSO integration. You can call it anything that makes sense for you. Ex: https://mypage.status.page/login/subscribers1
RoleSelect the Role of the users for this integration. See Roles for more information.
Is Default RoleIf the default is not set, the first integration for the role will be chosen if the user is using our former standard role-based SSO paths like: /login/employee...
TypeSelect the SSO type from the dropdown. Use SAML 2.0 if the type is not defined in the dropdown
Enable Email NotificationsAutomatically sign up a Subscriber or Employee for Email notifications
Target URLEnter the SSO Target URL unique the Duo App which you can find in the setup instructions labeled as your Identity Provider Single Sign-On URL.
Map Groups AttributeOptionally, you can add a Group Attribute. See Groups Attribute
Append Domain Name to User NameIf your SSO doesn't send the username over as an email address @somewhere.com will need to be appended to the username to work with our system. Add the domain here.
CertificatePaste a copy of your X.509 Certificate

Signing In

Now your integration is complete and the users you granted access to can sign into StatusCast using their SSO credentials.

Commonly used URL paths for each of the roles are listed below, but you can now choose these in the integration settings. Be sure to send your users to the appropriate path.

Subscriber > https://[yourapp].status.page/login
Employee > https://[yourapp].status.page/login/employee Manager > https://[yourapp].status.page/login/manager Administrator > https://[yourapp].status.page/login/admin Company Administrator > https://[yourapp].status.page/login/companyadmin