Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: DAV login with email address: Call to a member function getUID() on null #42961

Closed
4 of 8 tasks
ChristophWurst opened this issue Jan 19, 2024 · 3 comments · Fixed by #42971
Closed
4 of 8 tasks

Comments

@ChristophWurst
Copy link
Member

⚠️ This issue respects the following points: ⚠️

Bug description

https://nextcloud-gmbh.sentry.io/issues/4892762928 popped up with the deployment of a 28.0.2.0 setup.

Bildschirmfoto vom 2024-01-19 12-52-33

Steps to reproduce

  1. Send DAV request using the email address as username

Expected behavior

Login works

Installation method

None

Nextcloud Server version

28

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

@ChristophWurst
Copy link
Member Author

ChristophWurst commented Jan 19, 2024

If the regression is from within the user session, there are only three new commits since 28.0.1

980b14f -> \OC\User\Session::tryTokenLogin is not used by the dav auth plugin
360e7ff
1712df7

@ChristophWurst
Copy link
Member Author

1712df7 actually sounds super relevant

👀 @juliushaertl

@ChristophWurst
Copy link
Member Author

20240119_135342

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

Successfully merging a pull request may close this issue.

2 participants