-
Notifications
You must be signed in to change notification settings - Fork 78
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
Registration is failing with broken old records in the database #250
Comments
There should not be a trailing slash on that url |
Still getting the error if I remove the slash from the path |
Is it only broken for me, or nobody upgraded yet? I still can't register anyone |
I just tried it again on my local test instance and it works pretty fine here. |
Done |
Can you try the following change? I can see the error happening on your instance, but I can not reproduce an issue locally. |
Still giving the same error Tried disabling the OIDC, no effect |
Ahh! CILogon now works, but not the regular registration |
Same issue. Updated from 19.0.4. to 20.0.1 |
No issue on fresh install, seems to be upgrade. |
Found the issue: If registration email address has been used previously and the 'secret' field in the oc_registration.client_secret is null, you receive an error 500. If you remove the oc_registration record and allow it to be re-created then everything is fine. |
Cleared a bunch of stale records from the table, and it works now. |
The question is why you have no client secret on those entries anyway. Because it's always created and never reset, as we only ever delete the full row.
Sure, there is a |
I hit the same bug on my instance, there are quiet a few rows in the oc_registration table with secret set to NULL. Most of them are more than a year old, there is really a need for a job to purge old entries. Looking at this I'm also asking myself if there is any limit on the number of open request, or can an attacker just let open request pile up until the disk is full? |
There will never be a limit. There are otherways you could create problems like this. |
Steps to reproduce
Expected behaviour
Registering works fine
Actual behaviour
Fails with 500 error.
Logs:
Server configuration
Operating system:
Container
Nextcloud version: (see Nextcloud admin page)
20.0.0
Updated from an older Nextcloud/ownCloud or fresh install:
Updated from 19.0.4
Signing status:
Signing status
List of activated apps:
App list
The content of config/config.php:
Config report
Are you using external storage, if yes which one: local/smb/sftp/...
cephFS
Are you using encryption: yes/no
no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
no
Browser log
Browser log
The text was updated successfully, but these errors were encountered: