Jira Integration | Detect Cloud deployment via serverInfo API instead…#668
Open
Chennoy wants to merge 1 commit intoaquasecurity:postee-for-enterprisefrom
Open
Jira Integration | Detect Cloud deployment via serverInfo API instead…#668Chennoy wants to merge 1 commit intoaquasecurity:postee-for-enterprisefrom
Chennoy wants to merge 1 commit intoaquasecurity:postee-for-enterprisefrom
Conversation
… of URL suffix Jira Cloud instances with custom domains (not ending in "atlassian.net") were misclassified as Server type deployement, causing user search and PAT validation to use the wrong API paths. Replaced the URL-based check with a /rest/api/2/serverInfo probe that reads the deploymentType field from the API. The URL check is kept as a fallback when the probe fails, preserving backward compatibility. Also refactored Init() to share a single client across the serverInfo probe and board fetch.
katy-rotman-aqua
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira Cloud instances with custom domains (not ending in "atlassian.net") were misclassified as Server type deployement, causing user search and PAT validation to use the wrong API paths. Replaced the URL-based check with a /rest/api/2/serverInfo probe that reads the deploymentType field from the API. The URL check is kept as a fallback when the probe fails, preserving backward compatibility. Also refactored Init() to share a single client across the serverInfo probe and board fetch.