I integrated the zendesk Single Sign On using JWT several months ago and experienced no issues with customer authentication until this week. Our support team started receiving complaints from some of our customers this week where users that had logged in (authenticated) with our web app but could not access the Zendesk knowledge base. The issue seems at this point to be related to new user accounts.
I am getting the following error message appended to the URL on zendesk authentication failure:
kind=error&message=Please+use+one+of+the+options+below+to+sign+in+to+Zendesk.
Has anyone run into this issue or know what this error indicates?
The issue might be related to this:
If your Zendesk is closed or restricted, and a user tries to sign in
with a different email than the one in Zendesk Support, their request
will be rejected (see Enabling social and business single sign-on )
The original discussion was removed from zendesk site for some weird reason:
https://webcache.googleusercontent.com/search?q=cache:QjwCf_sEY4oJ:https://support.zendesk.com/hc/es/community/posts/115008094888-Zendesk-SSO-error-Please-use-one-of-the-options-below-to-sign-in-to-Zendesk+&cd=1&hl=ru&ct=clnk&gl=ru
I actually solved this for our installation last night. I finally realised what I was doing wrong. I had only turned on SSO for end-users so when I tired to test it, as an agent, it was showing this error. So turning on SSO also for agents solved this.
Thanks for sharing, Greg! That's a good tip.
Yes, thanks Greg! that resolved my issue with this error as well!
Thanks for sharing your resolution, Greg! Arlen, I'm glad you got it working!
Related
I have a custom developed Windows service that until recently used basic authentication to access an O365 mailbox over POP and pull the contents on a predefined schedule. Microsoft recently announced that they were dropping the support for basic authentication and I should be using OAuth 2 instead. I have followed the steps in this article and my application has the necessary permissions in the Azure portal. I'm still running into an issue.
I can successfully generate the OAuth token. When I try to use said token to authenticate I get "Authentication failure: unknown user name or bad password". No further details are available. I tried Microsoft support but they only referred me to guides I've already followed. Any help is greatly appreciated!
After three days of scratching my head I finally stumbled upon the answer. Turns out that according to Microsoft ObjectID is different from ObjectID. Because logic! Two different interfaces for the same thing with two different ObjectIDs. You need the one on the right when giving permissions to the mailbox.
My app has been OAuth verified for youtube and youtube.upload.
When I OAuth with these scopes, it's still not working.
I get the following in the web browser as before verification. They closed out my ticket, so I have no means to contact them.
Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In.
If you are a developer for this application, please submit a verification request to re-enable Sign in with Google. Learn more
Please advise
Sign in with Google temporarily disabled for this app This app has not been verified yet by Google in order to use Google Sign In.
If you are a developer for this application, please submit a verification request to re-enable Sign in with Google. Learn more
The message you are getting clearly states the issue. Your application is not verified or its verification has bee removed. In order to fix this you must go thought he verification process. You might want to check your email and see if there is any messages from google as to why your verification was removed. I have seen several posts like this over the last week it seams Google may be going though projects.
Pls, I really need help asap.I have created a dialogflow bot for an institution and it is to integrated into twitter. after following dialogflow's documentation, I managed to place it on the company's official twitter page. but now, I'm having an issue with communicating with the bot. I always have to send a DM or tweet to the page in order to get response from the bot. but, the company uses the same page to receive customer complaints. Please, isn't there anyway that I could host the bot on the page and get users to be able to chat with the bot and/or also with customer care.
You can try deploying it on a dummy page for the time being and fixing the issue.
If I'm misunderstanding something here then I'm sorry but from what I can tell, you made a bot and deployed it on the official twitter page but the behaviour was not as expected. This has lead to the bot replying to customers when it wasn't supposed to? I'm sure you're in a hurry but its not perfectly clear but that's what I got from the post
Also, its always better to test on a dummy page before deploying to the official page.
Good day guys,
Please, I am working on a project that requires setting up Google Adwords account in order to use the API. I am using the Python Client Library. I am getting a DEVELOPER_TOKEN_NOT_APPROVED error when I run my test application.
After a lot of research on the issue, I figured maybe I didn't set up the production and test accounts properly which I am still struggling with. I really hope you can put me through the process as I am running against time.
Looking forward to your help
Thank you very much.
You need Developer Token from production account, but until approval is pending you need authorize API call only for test AdWords account. You need two different Google accounts. You must get Refresh Token after login to your another Google account for testing purpose.
More info: https://developers.google.com/adwords/api/docs/guides/accounts-overview#test_accounts
I've been searching the docs and googling like a maniac, but I can't find the sandbox openid endpoint/identifier for paypals sandbox. I've got the productive url, https://www.paypal.com/webapps/auth/server, but to use it I need an approved app.
I just want to test the flow, before I go through the hastle of creating an app.
I finally got the answer from PayPal: The OpenId/Oauth stuff is currenlty in a closed beta.