1. Login your Vast Conference account

  2. Go to Account > Single Sign-On

  3. Select +Add New Identity Provider

  1. Select Okta and Continue

  1. Select an Application: (one at a time)

  2. Vast Conference (Website)

  3. Vast Conference (Meeting App)

  1. In Okta, go to Applications

  2. Click on Add Application

  1. Click Create New App

  1. Set Platform to Web

  2. For Sign on method, select SAML 2.0

  3. Click on Create

  1. For App name, enter Conference Calling

  2. Upload our logo

  3. Download here

  1. Enter in the Single sign in URL (found in your Vast Conference account)

  2. Enter in the Audience URI (SP Entity ID) (found in your Vast Conference account)

  1. For Name, enter Email

  2. For Value, select user.email

  3. Then click Next at the bottom of the page

  1. Select I’m an Okta customer adding an internal app

  2. Check the box for This is an internal app that we have created

  3. Click Finish

  1. On the next page, click on Sign on

  2. Click on View Setup Instructions

  1. The following items are needed to complete the set up within your Vast Conference account

  1. Continuing the Okta set up from your Vast Conference account, click Continue

  1. Enter in your SAML 2.0 Endpoint

  2. Enter in your Identity Provider Issuer

  3. Paste your Public Certificate

  4. Click Save Configuration

  1. Once completed, you’ll see Oktalisted as an Identity Provider

This document provides step-by-step information on how to configure Vast Conference applications in the Okta environment. 

Introduction

Two applications need to be added to the Okta environment:

  1. Vast Conference (Meeting App)

  2. Vast Conference (Website)

Vast Conference (Meeting App)

This application will be used to configure Single Sign-On (SSO) for the Web Meeting Host application.

1. Log in to your Okta environment as a user with administrative privileges. 

2. Click on the Admin button.

3. Go to Applications -> Applications menu item. 

4. Click on the Add Applications shortcut.

5. Click on the Create New App button.

6. In the dialog box that appears, select Web from the Platform dropdown option and SAML 2.0 for the Sign on method, then click the Create button.

7. In Step 1 General Settings enter “Web Meeting” in the App name field. Upload the logo file by browsing for vast-logo-app.png. Click the Upload Logo button. 

8. Click the Next button.

9. Step 2 Configure SAML:  In Section A SAML Settings, paste the URL below into the Single sign on URL field.

https://app.vastconference.com/sso/app/assertionconsumerservice.aspx

11. In the same section, under ATTRIBUTE STATEMENTS (OPTIONAL), add an attribute with these values: Attribute Name – Email, Name Format – Unspecified, Value – user.email 

12. Click Next to continue.
13. In Step 3 Feedback, select I’m an Okta customer adding an internal app and check the box for This is an internal app that we have created, then click Finish.

14. The Sign On Methods section of your newly created Web Meeting application will appear with a button to View Setup Instruction. 

15. Click the View Setup Instructions button.
16. A new page called How to Configure SAML 2.0 for Web Meeting Application will appear.

17. This page will provide:

  • Identity Provider Single Sign On URL 

  • Identity Provider Issuer 

  • X.509 certificate 

This information needs to be provided to the Vast Conference team to complete configuration on their side.

(Single Sign-On URL displayed in the above screenshot contains a test environment address as base address. It will contain the base address of the customer’s Okta organization.)
18. Users can be assigned to the application from Assignments section.

Vast Conference

This application will be used to configure Single Sign-On (SSO) for Vast Conference (Website).

  1. Click on the Create New App button.

  2. In the dialog box that appears, select Web from the Platform dropdown option and SAML 2.0 for Sign on method, then click the Create button.

3. In Step 1 General Settings enter “Vast Conference” in the App name field. Upload the logo file by browsing to vast-logo-website.png. Click the Upload Logo button. 

4. Click the Next button.
5. In Step 2 Configure SAML: In Section A SAML Settings, paste the URL below into the Single sign on URL field.

https://www.conferencecalling.com/admin/sso/web/assertionconsumerservice.aspx

6. In the Audience URI (SP Entity ID) field enter “ConferenceCalling”.

7. In the same section, under ATTRIBUTE STATEMENTS, add an attribute with below values.

Attribute Name – Email, Name Format – Unspecified, Value – user.email 

8. Click Next to continue.
9. In Step 3 Feedback, select I’m an Okta customer adding an internal app, and check the box for This is an internal app that we have created, then click Finish.

10. The Sign On Methods section of your newly created Vast Conference application will appear with a View Setup Instructions button.

11. Click the View Setup Instructions button. A new page called How to Configure SAML 2.0 for Vast Conference Application will be displayed.

12. This page will provide:

  • Identity Provider Single Sign On URL 

  • Identity Provider Issuer 

  • X.509 certificate 

This information needs to be provided to the Vast Conference team to complete configuration on their side.

(Single Sign-On URL displayed in the above screenshot contains a test environment address as base address. It will contain the base address of the customer’s Okta organization.)

13. Users can be assigned to the application from the Assignments section.

Information Needed to Provision Okta SSO 

The Vast Conference team needs the following information to complete the configuration on their side:

1. From Setup instructions of Vast Conference application:

  • Identity Provider Single Sign On URL 

  • Identity Provider Issuer 

  • X.509 certificate 

2. From Setup instructions of Vast Conference application:

  • Identity Provider Single Sign On URL 

  • Identity Provider Issuer 

  • X.509 certificate 

3. Site Address 

This can be any unique name like “vast”. This will be used for identifying the customer’s Okta organization. This will need to be entered by the Okta users when using Single Sign-On initiated from the Vast Conference applications, such as when a user clicks Login with Okta after launching Web Meeting.

Below is a sample page requesting the Site Address.

For chiclet-initiated sign in, this won’t be needed since users are requesting access from customer Okta organization itself.

Did this answer your question?