Configuring UTF-8 Encoding for BroadWorks Authentication

list-menuFeedback?
Set UTF-8 encoding for BroadWorks authentication to handle special characters in passwords.

Authentication Mode

Decide how you want subscribers to authenticate when they log in to Webex. You can assign the mode using the Authentication Mode setting in the Onboarding template. The following table outlines some of the options.

This setting has no effect on login to the User Activation Portal. Users who sign in to the portal must enter their BroadWorks user ID and password, as configured on BroadWorks, irrespective of how you configure Authentication Mode on the Onboarding template.

Authentication Mode BroadWorks Webex
Primary user identity BroadWorks user ID Email address
Identity Provider

BroadWorks.

  • If you configure a direct connection to BroadWorks, the Webex App authenticates to the BroadWorks server directly.

    To configure a direct connection, the Enable direct BroadWorks authentication check box must be checked within the BroadWorks cluster configuration on Partner Hub (by default, the setting is unchecked).

  • Otherwise, authentication to BroadWorks is facilitated through an intermediary service that is hosted by Webex.

Cisco Common Identity
Multi-factor authentication? No Requires Customer IdP that supports multi-factor authentication.

Credential validation path

  1. Browser is launched where user supplies email to initial login flow and discover their authentication mode.

  2. Browser is then redirected to a Webex hosted BroadWorks login page (This page is brandable)

  3. User supplies BroadWorks user id and password on the login page.

  4. User credentials are validated against BroadWorks.

  5. On success, an authorization code is obtained from Webex. This is used to obtained necessary access tokens for Webex services.

  1. Browser is launched where user supplies email to initial login flow and discover their authentication mode.

  2. Browser is redirect to IdP (either Cisco Common Identity or Customer IdP) where they will be presented with a login portal.

  3. User supplies appropriate credentials on login page

  4. Multi-factor Authentication may take place if the Customer IdP supports this.

  5. On success, an authorization code is obtained from Webex. This is used to obtained necessary access tokens for Webex services.

For a more detailed breakdown of the SSO login flow with direct authentication to BroadWorks, see SSO Login Flow.

UTF-8 Encoding with BroadWorks Authentication

With BroadWorks authentication, we recommend that you configure UTF-8 encoding for the authentication header. UTF-8 resolves an issue that can occur with passwords that use special characters whereby the web browser does not encode the characters properly. Using a UTF-8 encoded, base 64-encoded header resolves this issue.

You can configure UTF-8 encoding by running one of the following CLI commands on the XSP or ADP:

  • XSP_CLI/Applications/WebContainer/Tomcat/GeneralSettings> set authenticationEncoding UTF-8

  • ADP_CLI/Applications/WebContainer/Tomcat/GeneralSettings> set authenticationEncoding UTF-8

Was this article helpful?
Was this article helpful?