I have someone run a script which makes calls to REAT API every few minutes and for some reason that script fails and throws errors in my logs.
How do i disable any calls made to REST API?
Rahul
This similar thread might help: https://answers.atlassian.com/questions/177821/how-to-stop-jira-making-rest-api-calls
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello.
In Jira 7.3.2, the settings "Accept remote API calls" is no more available ? Someone knows how to restore this feature ?
Thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It was removed late in 6.something if my memory serves.
This is because Jira now uses its own REST interface to fetch some of its own data. Turning it off will stop a good chunk of Jira from working.
So, you can't disable it any more.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Presumably there's a way to require authentication on these APIs, though? I can see private information on publicly accessible API endpoints.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
All the REST calls require authentication.
If you're seeing "private" information, it is available becuase it has been made public
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you can see "private information" over the REST API, then you have configured your system such that it is NOT private.
The REST API respects the security you set up in the application. If you want to secure your data, then disable access to it with your permission schemes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, this is precisely the case. But it would be very useful for there to be a setting to suppress all publicly-shared content, so that administrators could override settings to ensure all content were only available at a maximum to authenticated users within the instance.
That seems relatively easy to for user lists. But it is considerably more onerous to unshare boards and filters that have been inadvertently made public.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But there's a load of publically shared information Jira needs in order to function now. So you can't turn it off.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.