Chat OAuth After Legacy Upgrade | Community
Skip to main content

Chat OAuth After Legacy Upgrade

  • March 8, 2021
  • 5 replies
  • 0 views
R

Hello,

My company has recently migrated from the legacy chat-only zopim accounts. Now, for an agent to access zopim, they cannot log in through the zopim login screen. Instead they have to login to support and navigate to chat. 

The issue with this is that I cannot obtain an access token via OAuth for the chat API if I cannot login to the zopim login screen. Also, I cannot use the confidential grant because the OAuth client needs to have "client_type": "confidential", which requires an API call to change.

 

What is the recommended way to obtain an access token for Chat API endpoints once the chat-only zopim login screen is no longer able to be used? Is there a way to re-enable logging in through zopim for a specific account, perhaps?

    5 replies

    Greg29
    • Greg29
    • March 8, 2021

    Hi Ryan! If you are using the new Chat, you just need to follow these instructions to get this setup! Feel free to drop a line in here if you run into any issues.

    R
    • Ryan31
    • Author
    • March 9, 2021

    Thanks for the response, Greg.

    The issue with what you provided is that the Implicit OAuth flow eventually takes me to the Zopim chat login screen. I'm ONLY able to log in through Zendesk support and then navigate to the chat. I cannot login through the Zopim Chat screen.

    I thought disabling the Zopim login was a part of the upgrade to integrated chat, but if you think I should be able to log into that Zopim screen, is there maybe some property set to disable Zopim login directly?

    Greg29
    • Greg29
    • March 9, 2021

    Hi Ryan! The instructions that I provided are for exactly your situation. Did you run into any problems when you tried following those steps?

    To answer your question, for an integrated account, there is no way to login to Zopim directly. 

    R
    • Ryan31
    • Author
    • March 9, 2021

    Hmm, maybe I am missing something. I appreciate the patience!

    Both the Implicit Grant flow and the Authorization code flow eventually get to the part where you have to authenticate by logging in. In both flows, you have to navigate to this url (Once replacing the necessary values of CLIENT_ID and SUBDOMAIN)

    https://www.zopim.com/oauth2/authorizations/new?response_type=token&client_id=CLIENT_ID&scope=read%20write&subdomain=SUBDOMAIN

    However, this url takes me to the Zopim Login Screen. Since it is an integrated account, I am unable to log in to obtain an access token.

    (Specifically Step 4 of the Implicit Grant Flow) (4. The call will be made, possibly asking you to log in and select 'Allow' to generate the token.)

    R
    • Ryan31
    • Author
    • March 10, 2021

    Update: I found my issue.

    For anyone having a similar issue, my issue was that I had an incorrect subdomain value in the URL. The zopim login screen appears when the subdomain is not included/incorrect. With the correct subdomain value, the correct(support/integrated) login screen appears instead of the Zopim screen.

    Thanks for the help Greg. As always, just a small detail was missed on my end.

    Terms & ConditionsCookie settingsAccessibility statement