We are not able any more to access our (self-hosted) JIRA software via REST API.
It worked without problems but since about one weeks JIRA reports authentication errors.
We tested with different clients (PyCharm, GitLab, JIRAClient) and from different IP Addresses. All of them report authentication problems (although I definitely entered the correct passwort)
Dear @Robert Hölzl,
this sounds like something spooky. But in the end something must have changed in your system. Either:
Can you find out, what change has been made since the past week?
So long
Thomas
The only known change is the firewall (its a simple NAT router without complex filtering or introspection between us in intranet and jira in intranet). To be sure that this is not the problem I connected to JIRA already via Mobile Phone to avoid this router => same result.
----
But then I looked into the JIRA REST API and saw, that the URL "https://jira.baltech.de/rest/api/latest/issue/FW-1" should be usable for testing. Requesting this URL on a browser that is logged in (via cookie) works fine (I get the expected JSON data). Running it on a browser which is not logged in returns:
"{"errorMessages":["You do not have the permission to see the specified issue.","Login Required"],"errors":{}}"
I expected the not-logged-in browser to ask me for username/passwort?!?
Is the browser usable as "referenz test" tool at all, to check if JIRA REST API installation is working/get clear error messages?
All other JIRA clients I am using are reporting very less information about the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Robert Hölzl,
the browser is "partially" usable. Best you download a browser extension like "RESTClient". There you use "basic authentication" and add as custom header "Content-Type: application/json" when POSTing data to the REST API.
So long
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the meantime it works again. I don't know why (the setup was not changed at all)...
But thanks for your hint.
If the problem occurs again, I have a tool to identify if the JIRA server or the JIRA client causes trouble.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, so the question is what did you change (probably in Jira, as you've tried different clients)?
And what are the authentication errors you get? They might help you locate what changed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.