Problem authenticating form Chrome Extension for Google

  • 0
  • 2
  • Question
  • Updated 6 months ago
  • In Progress
I have added the Chrome Extension for Google.  The sidebar loads with a "Login with RingCentral" button.  When I click the button it collects my phone number and password in a separate popup window, but then that popup sits at "Please wait..." and never completes the authentication.  I'm on the latest Chrome on the latest OS X.

Any ideas?
Photo of Al Wasserberger

Al Wasserberger

  • 80 Points 75 badge 2x thumb

Posted 6 months ago

  • 0
  • 2
Photo of Saadet - Community Support

Saadet - Community Support, Official Rep

  • 32,896 Points 20k badge 2x thumb
Hi Al, do you have a screen shot you could share? Do you happen to have Single Sign-On enabled?
Photo of Josh Harrington

Josh Harrington

  • 80 Points 75 badge 2x thumb



Same problem here. I checked for chrome updates cleared cache and cookies uninstalled and reinstalled extension and still occurring. 
Photo of Josh Harrington

Josh Harrington

  • 80 Points 75 badge 2x thumb
Also Im not using single sign on.
Photo of Saadet - Community Support

Saadet - Community Support, Official Rep

  • 32,896 Points 20k badge 2x thumb
Hello Josh & Al,

Please open a case with us. Include the screen shots you provided as well as the HAR Logs

Feel free to provide your case number so I can keep an eye on it.
(Edited)
Photo of Joshua Reed

Joshua Reed

  • 100 Points 100 badge 2x thumb
I am having a user with the same exact issue. I will submit a ticket with this data as well, but wanted to voice the issue here for a 3rd person.
Photo of Josh Harrington

Josh Harrington

  • 80 Points 75 badge 2x thumb
Case # 06634294
Photo of Joshua Reed

Joshua Reed

  • 100 Points 100 badge 2x thumb
Ticket #06634322
Photo of Saadet - Community Support

Saadet - Community Support, Official Rep

  • 32,896 Points 20k badge 2x thumb
Thank you!
Photo of Joshua Reed

Joshua Reed

  • 100 Points 100 badge 2x thumb
I got a response from support that this was a wide issue they were working on and that it was now resolved. Testing it it now works on my end!