-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Closed
Labels
issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/bug
Description
- Gitea version (or commit ref):
- Git version: 1.11.1
- Operating system: ubuntu:bionic-20180821
- Database (use
[x]
):- PostgreSQLMySQLMSSQLSQLiteTo pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)NoNot relevantTo pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
- Log gist:
N/A
Description
When I check for users with the Last Sign-In status Never Signed-In
, I find users that have published repos on the platform. This shouldn't be possible.
Screenshots
Metadata
Metadata
Assignees
Labels
issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/bug
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
jolheiser commentedon Feb 20, 2020
Is there a chance someone transferred a repo to this account?
Or that the user created the repo via push-create if enabled before logging in?
lunny commentedon Feb 21, 2020
There is a known issue that if user only push/pull via git, the
Last Sign-In
didn't update.rnowak commentedon Feb 22, 2020
Chiming in to add that this is also the case if the user authenticates via a header set in REVERSE_PROXY_AUTHENTICATION_USER both for the web interface as well as git interactions over https.
stale commentedon Apr 23, 2020
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
fnetX commentedon Apr 7, 2021
AFAICT this is also the case if a user registers and does actions within pers first session (this also explains how a user could create a repo which is not possible with push / pull alone).
zeripath commentedon Apr 8, 2021
Ok that's a much simpler bug to fix!
furai commentedon Apr 10, 2021
I get the same issue - I have gitea behind reverse proxy and last sign-in doesn't update.
(Also for some reason when I log-in, I get presented with a blank screen until I refresh, and I don't know why.)
zeripath commentedon Apr 10, 2021
I think that that this has been patrially fixed already in 1.14+ probably earlier (excepting potentially ReverseProxy)
SetLastLogin()
does not appear to be called on API logins. Is it possible therefore that these are creations from the API?zeripath commentedon Apr 10, 2021
This should be fixed by #15304
wolfogre commentedon Nov 9, 2022
The case should be fixed by #21731.
1 remaining item