Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When someone clicks the "new branch" link on a gitlab-powered issue, if they are not logged into drupalcode.org they are shown a 404 page, instead of a 403 page that would indicate the person needs to log in.
Issue fork drupalorg-3155441
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
drummAssuming there’s nothing completely off about the state of your cookies, and the account being set up correctly - we should be able to detect when you aren’t logged into git.drupalcode.org in one of the JS fetches. I believe we could then complete the SSO process in a hidden iframe, so you are always logged in shortly after viewing an issue page with a fork.
Comment #3
mglamanHonorable +1, I just ran into this and didn't notice I was logged out of GitLab!
Comment #4
drummComment #6
drummPages with issue forks now do a request to check if you are logged into GitLab. If you are not, an
iframe
to initiate sign-on is added. This works well in Firefox and Chrome.I discovered this isn’t working at all for Safari, including the existing places we do this, #3157062: GitLab SSO does not automatically log in on Safari.