User Sign-In and Authentication Flow for Webex App

list-menuFeedback?
Learn about the sign-in process for Webex app users, including the SAML SSO flow with BroadWorks authentication and user interactions.

User Interactions

Sign In

  1. The Webex app launches a browser to Cisco Common Identity (CI) to allow users to enter their email address.

  2. CI discovers that the associated customer org has the BroadWorks IDP Proxy (IDP) configured as their SAML IDP. CI redirects to the IDP which presents the user with a sign-in page. (The Service Provider can brand this sign-in page.)

  3. The user enters their BroadWorks credentials.

  4. Broadworks authenticates the user through the IDP. On success, the IDP redirects the browser back to CI with a SAML Success to complete the authentication flow (not shown in diagram).

  5. On successful authentication, the Webex app obtains access tokens from CI (not shown in diagram). The client uses them to request a BroadWorks long-lived Jason Web Token (JWT).

  6. The Webex app discovers its calling configuration from BroadWorks and other services from Webex.

  7. The Webex app registers with BroadWorks.

Sign In from a User Perspective

This diagram is the typical sign-in flow, as seen by the end user or subscriber:

  1. You download and install the Webex app.

  2. You may have received the link from your service provider, or you can find the download on Webex downloads page.

  3. You enter your email address at the Webex sign-in screen. Click Next.

  4. Typically, you’re redirected to a Service Provider branded page.

  5. That page may welcome you by your email address.

    If there’s no email address, or if the email address is wrong, enter your BroadWorks user name instead.

  6. Enter your BroadWorks password.

  7. If you signed in successfully, Webex opens.

Call Flow—Corporate Directory

Call Flow—PSTN Number

Presentation and Sharing

Start a Space Meeting

Was this article helpful?
Was this article helpful?