Login to gitlab using github
Wait 1 day
Access the site again
What is the current bug behavior?
I get logged out!!!!
What is the expected correct behavior?
I don't get logged out.
This is a huge hassle in using Gitlab. I am actively working on a project, I am on that site every day. Why does it log me out? Set that security token to 1 month expiry and auto-renew it every time I am on the page.
Possible fixes
Set that security token to 1 month expiry and auto-renew it every time I am on the page.
Boom you've increased usability of the site by 1000%
That's a really simple change. I honestly don't know why it's logging me out at all? Is your usual customer sitting in a library using a public PC? Normally we are on our devices, and they're locked down on their own, there's no need to log anyone out.
Proposal
There may be different reasons for this issue to occur. For this issue, we will focus on adding the "Remember Me" checkbox to the Group SAML sign-in. Due to the existing functionality of SAML on GitLab.com, this means we will still redirect through the SAML flow once every 24 hours.
@n131 - Can you add your browser details to this bug report? I'm not seeing the same behavior and do not see other bug reports for this. For reference, I am using Chrome 79 or Firefox 71 on Mac OS 10.15.
@jeremy - would this bug report be under ~"group::access" or some other group?
Can confirm that this is happening for me on all my devices/browsers, despite selecting 'remember me'.
This is particularly annoying on the iPhone, where signing in, especially with 2FA, is already cumbersome. On iOS, gitlab.com logs me out after a day or maybe sooner. Not conducive to quickly entering issues on the go, especially as there isn't a native iOS app.
I'm experiencing getting logged out every day as well, if performing forensics on my account information would help. Also, I get a cloudflare warning "checking your browser" everytime I navigate to gitlab for the first time every day, so it's possible for that to be related.
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.135 Safari/537.36 Edg/84.0.522.63
(But it happened in Chrome on a Mac before in the past as well)
@mushakov - Can you confirm this ~bug belongs on ~"group::access"? There seems to be a larger number of reports on this and the severity may need to be increased.
Happens to me too on self hosted GitLab Community Edition 13.4.1. I noticed that my session cookie is always set to expiration date: Session which doesn't make much sense.
Temporay workaround: Manually setting the expiration date on _gitlab_session seems to work for me. Needs to be done on every device.
Still annoying, though!
Copying some details here from my own experience - and from the closed duplicate:
This logout happens very frequently for me, but in batches.
I see that most of the folks above are getting logged out once a day, but my experience is sporadically more extreme.
For example, I may not be logged out of GitLab at all for a week or so, and then for a few days, I will be logged out multiple times per day.
Here's an example of a very common situation for me:
I am logged in
I begin an MR review
I leave a comment or do some other action like leaving a reaction emoji
I continue the review - fewer than 5 minutes elapse
I try to leave another comment or a reaction - an error occurs, which doesn't inform me that I've been logged out.
Because I have dozens of experiences with this, I know to refresh the page, after which I see that the header bar is the "Log in / Sign Up" button instead of my profile image
However, none of the error messages indicate that I've been logged out, they just say that submitting my comment (etc.) has failed.
I log back in
Fortunately, comments are cached locally, etc. so I can pick right back up
One note: I recall this happening maybe once while creating an MR. The data on the create MR page is not cached, so the outcome is either lose everything entered there or have the cognizance to open a new tab, sign in, then open a new create MR page (which is now properly authenticated), copy everything over and submit there. Of course, while crossing your fingers that the new authenticated tab doesn't get logged out in the mean time
On that note, I should say that Clicking the "Sign In" button causes a short load, and then "nothing" happens. I need to click "Sign in" again to get to the 2FA area (where it's waiting for the hardware generated code). Last time I tried logging in without hardware 2FA enabled, I don't recall this happening (6+ months ago?). So I naively suspect that hardware 2FA is causing issues with both requesting a login (by clicking "Sign in") and with staying logged in during an active session.
Not worth spending the time explaining the issue, this has been like that for over a year, and it is insanely simple to solve. Also, whatever you described is not what this post is about i believe.
OK. I just got kicked out of Gitlab to reauthenticate in the middle of creating a new Merge Request. Really Not Cool! I know people are trying to make this happen through proper channels and processes, but this is seriously a bad experience. What else can we do to help get this fixed?