Following the initial deployment of Jira Service Desk, to a limited user group, we are receiving reports of poor logon performance and with users repeatedly seeing “502 - Web server received an invalid response while acting as a gateway or proxy server”.
When users attempt to logon to JSD is this going back through to validate against our AD or is this going locally to the information already obtain by JSD for the frequent syncing of AD data?
Environment & Setup: Jira Service Desk has been deployed within our Azure environment, opting to use the server installation with a Azure Postgres database. The Azure VM is also within a Docker container, which is the standard practise for our DevOps deployments within our organisation.
Within JSD application we have connected through to our on premise Microsoft Active Directory obtaining all users within a specific group. Additionally we use Insight (3rd party plugin) to link to AD using the same query to obtain user information and extract more information (phone number, email address etc).
On October 20, 2021, Atlassian published a security advisory for Jira Service Management. The full advisory is available at this link. We've seen a number of questions already asking for...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event