AVAYA: RSA Authentication Error "Failed to Log In"

Avaya authentication services have been fully restored. The issue was identified as a result of a recent RSA patch, which was rolled back overnight. System stability has been confirmed following the reversion. We appreciate your patience and please contact the Tech Deck directly should you require further assistance.

Service has been restored following the implementation of an interim workaround. RSA MFA authentication for internal network traffic has been temporarily disabled while a permanent resolution is in progress. The CEC should now be able to log in without issue.

If you continue to experience login issues with Salesforce and/or Avaya, please clear your browser data, relaunch all browser windows, and attempt to reauthenticate.

If the issue persists, please contact the Tech Deck for further assistance.

We continue to investigate the Avaya/Salesforce issue impacting both the GCC and Pro Call Centers (as this is specific to call centers accessing Avaya within SF). At this time, a permanent resolution has not been identified; however, the team is actively working toward a fix. Workaround (GCC CEC agents):

• Launch Big Avaya - https://na-01.workspaces.avayacloud.com/services/ApplicationCenter/workspaces
• Return to Salesforce and refresh the page
• This should allow successful logon

Additional details are available in the Tech Slack channel. You may also contact the Tech Deck for assistance. We will continue to provide updates as more information becomes available.

Tech Deck is aware of reports the CEC is experiencing errors when authenticating to Avaya within Salesforce. The issue has being investigated. An estimated time to resolution is not yet available. Updates will be provided as more information becomes available.