Summary:
We are trying to integrate our self-hosted GitLab instance with Jira Cloud using the GitLab for Jira app, but encountering a login issue.
Details:
Our self-hosted GitLab server is accessible at:
https://gitlab.example.com/gitlab
(Note: the /gitlab path is intentional due to internal requirements.)
When attempting to log in to GitLab from Jira (via the GitLab for Jira app) to select projects for integration, the login window fails with a 404 Not Found error.
Upon inspecting the login URL, we noticed that an additional /gitlab is being appended, resulting in a malformed address like:
https://gitlab.example.com/gitlab/gitlab/
This causes the 404 error during the login attempt.
Request:
Is there a way to configure the GitLab for Jira app to respect the custom base path (/gitlab) without appending it again? Any advice or workaround would be greatly appreciated.
Hey @Marc -Devoteam- thanks for your response,
We followed the official GitLab ↔ Jira integration guide but encountered a problem during the login step.
Our self-hosted GitLab instance is available at {{https://example.com/gitlab}}, yet when Jira redirects us for authentication it appends another “/gitlab”, resulting in {{https://example.com/gitlab/gitlab}}, and the login fails.
I hope that clarifies the issue—let me know if you need more details.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The app is probably not able to use a custom defined path, on doubts contact Atlassian Support.
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.