Skip to content

Users Never Signed-In, yet have repos published #10374

@sefsh

Description

@sefsh
  • Gitea version (or commit ref):
  • Git version: 1.11.1
  • Operating system: ubuntu:bionic-20180821
  • Database (use [x]):
    • PostgreSQL
      MySQL
      MSSQL
      SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
      No
      Not relevant
  • 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

bild

Activity

jolheiser

jolheiser commented on Feb 20, 2020

@jolheiser
Member

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

lunny commented on Feb 21, 2020

@lunny
Member

There is a known issue that if user only push/pull via git, the Last Sign-In didn't update.

rnowak

rnowak commented on Feb 22, 2020

@rnowak
Contributor

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.

2020-02-22 14_26_46-User Accounts

stale

stale commented on Apr 23, 2020

@stale

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.

added
issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implemented
on May 6, 2020
fnetX

fnetX commented on Apr 7, 2021

@fnetX
Contributor

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

zeripath commented on Apr 8, 2021

@zeripath
Contributor

Ok that's a much simpler bug to fix!

furai

furai commented on Apr 10, 2021

@furai

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

zeripath commented on Apr 10, 2021

@zeripath
Contributor

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).

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

zeripath commented on Apr 10, 2021

@zeripath
Contributor

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.)

This should be fixed by #15304

wolfogre

wolfogre commented on Nov 9, 2022

@wolfogre
Member

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).

The case should be fixed by #21731.

1 remaining item

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @lunny@techknowlogick@sefsh@rnowak@zeripath

        Issue actions

          Users Never Signed-In, yet have repos published · Issue #10374 · go-gitea/gitea