I'm using JIRA in the cloud (so the url I visit is .atlassian.net).
I've been trying to get and create issues using the JIRA API and this library https://bitbucket.org/farmas/atlassian.net-sdk/wiki/Home.
However I am getting authorization errors and since I know I have the correct login details, I was wondering if this would be related to the "Accept remote API calls" setting.
I followed the instruction here (https://confluence.atlassian.com/jira063/configuring-jira-options-683542606.html) but I can't see the "Accept remote API calls" setting. I should also mention that I am the account admin.
I'm wondering if this setting is only visible if you are hosting JIRA on your own server, or if there is something else I am missing.
Any help appreciated.
There is no setting to enable this on a Cloud instance and the remote API is enabled by default.
Related
We are setting up Google My Business using the following oauth instructions.
https://developers.google.com/my-business/content/notification-setup
However, there seems to be a process somewhere that keeps changing the settings and sending the notifications to a different pub/sub topic. So basically it appears to be making a PUT request to :
https://mybusiness.googleapis.com/v4/accounts/{accountId}/notifications
Is there a way to determine the source of the request ? There does not seem to be any instructions on how to access Google My Business API audit logs.
You should check who else has access to that location group, ideally through the GMB UI as that can give you an e-mail address hint:
I've got a simple Dialogflowbot that I'm trying to integrate with my Slack workspace.
I've made a Slack app for the bot.
I've added all the information in Dialogflow integration dialog.
On Slack app side I've set-up bot user, added event subscriptions (including link from DF) and set up OAuth scopes and added the URL.
However, the bot won't reply back. Everything looks fine in DF logs but I'm not getting responses in Slack. Previously I've been able to solve this kind of situation by clicking the 'Install to Slack' button under 'Manage distribution' -tab. However, now when I do that (and allow installation), I receive the following error message:
While starting bot the error appears:
Bot start error: oauth_authorization_url_mismatch
From Slack documentation I've found out that this means "The OAuth flow was initiated on an incorrect version of the authorization url. The flow must be initiated via /oauth/authorize." However, the OAuth URL Dialogflow provides is of form bots.dialogflow.com/slack/<TOKEN>/start.
I've
contacted both Slack and Dialogflow support
done bunch of Googling and
asked a few people that also work on Slack bots
but I've found nothing. Maybe someone here would have ran to the same issue would know what to do?
Recently the Slack team made a change in the oauth authentication with backward incompatible changes. This change break the integration with Dialogflow.
Fortunately, the old functionality has not been fully removed from Slack. In the link I shared above (here's again), at the bottom of the documentation there's an option to "Create a classic Slack app". If you click on it, you will be able to create a "legacy" bot and use follow the Dialogflow-Slack integration guide; it will work as intended.
An important thing to notice, is that you'll see an option to "Update Scopes". Be careful not to make this update, as this will change the authentication from classic to the new approach, and it will break the bot.
Finally, the Dialogflow team already knows about this issue and they're working to make the integration compatible with the new Slack authentication. You can subscribe to that IssueTracker (click the star next to the title) and get updates regarding its progress.
I installed JIRA Cloud for sheet add-on. While connecting with JIRA instead of connecting using Atlassian account I used the google account and thus not get authenticated and got this error message.
Now the problem is, even if I try the the same again and wants to use Atlassian account, its still throwing the same error and not allowng me use Atlassian account. Cleared cache, reinstall JIRA Cloud for sheet add-on but no luck.
Any idea?
I doubt you are still logged in with your google account into the Atlassian cloud Jira.
Wonder how? Can you try opening id.atlassian.com? At the very left bottom corner, click on your profile pic and logout. Login again with your correct id and password and you should be able to use your Jira cloud as usual.
Remember, when you login into any Atlassian Cloud instance you actually login into id.atlassian.com account which is used for authentication by all other atlassian cloud sites. To logout completely, change account login you need to go to id.atlassian.com.
I hope this helps you.
I am building a wordpress woocommerce site and am trying to get the users to login using G+.
Everything was going just fine till I changed the plugin I was using and added new redirect URLs to the OAUTH 2.0 Client ID.
Now the users get the error:
Access Not Configured. Google+ API has not been used in project
1033299751186 before or it is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/plus/overview?project=1033299751186
then retry. If you enabled this API recently, wait a few minutes for
the action to propagate to our systems and retry. Please notify about
this error to the Site Admin.
Any help would be appreciated.
Thanks
You need to go to google developer console as it says under the project 1033299751186 and enable the Google+ api.
Your project needs to have each of the different APIs enabled that it needs to access.
Look for API manager -> Enable APIs (its a tab at the top)
I use API Asana in "MyAsana" to follow my Workspace (Project) in Asana.
The API is used in 10 smartphones from different people to follow the task of projects.
After 2 days, the API does not respond. All applications authorized in Asana do not respond.
I reset the API & it works in MyAsana. and today the same problem.
I have to do a reset and change the API in all phones.
Error is: UNEXEPTED ERROR WHILE CONNECTING WITH ASANA.THIS IS MOST LIKELY A PROBLEM WITH ASANA SERVER. Please try again later.
How can I fix this please?
Asana is currently having some problems with its service and has had to temporarily shut down access to the API while it addresses them. Follow #asana on twitter and you should get a tweet when access is restored.