Jira Connect app cannot authenticate with GitLab in some browsers
Summary
When setting up the GitLab for Jira app, using Safari and or Edge, the user is prompted to sign in to GitLab in order to add a namespace. Even when signed into GitLab.com in a new tab, the "Sign in" error message is persistence.
Note: This bug was discovered using the latest version of Safari and Edge on MacOS. Other browsers and OSs should be tested. Chrome and FireFox seem to work as expected.
Steps to reproduce
- Using Safari, sign into your Jira account
- Install the app: https://marketplace.atlassian.com/apps/1221011/gitlab-for-jira?hosting=cloud&tab=overview
- Click "Get started"
- Try and add the name of a GitLab namespace you have access to that you want to link
- If you are not signed into GitLab.com, try signing in and try to add the namespace again.
Example Project
What is the current bug behavior?
What is the expected correct behavior?
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
Edited by Libor Vanc