Open dimanoga opened 1 day ago
We’re experiencing a very similar issue in our setup! We also use Nginx as a proxy for Jira with IP whitelisting, and have noticed the URL handling seems inconsistent, which causes authentication errors like the 401 Unauthorized you mentioned.
It would be great if the Jira team could help clarify or address this behavior. Thanks for sharing your experience—it’s helpful to know we’re not alone with this issue!
Bug summary
Hi there,
In our company, API access is provided through a white list system. To "fix" IP addresses, we use Nginx as a proxy server for accessing Jira. However, we have noticed that when we use the connection.issuel), in the dictresource method, the URL is replaced with one that Jira returns, rather than the one from which the request originated. Additionally, when updating issues using the issue.update method, the URL used is not the one that the authorization was initiated from, but rather the one provided by the Jira server.
Due to this, when attempting to update a task, we receive a 401 unauthorized error. We are hoping to resolve this issue and ensure that the correct URL is used for all API requests.
Could you please assist us in resolving this issue? We would greatly appreciate any assistance you can provide. Thank you in advance for your attention.
Is there an existing issue for this?
Jira Instance type
Jira Server or Data Center (Self-hosted)
Jira instance version
8.20.0
jira-python version
3.5.2
Python Interpreter version
3.11
Which operating systems have you used?
Reproduction steps
Stack trace
Expected behaviour
The Jira URL has not been replaced, but the one that was used for authorization is still being used,
Additional Context
No response