nextcloud / nextcloud/user_oidc
[help_request] Users disappear when switching from SAML to OpenIDconnect
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 181
- Forks
- 60
- Avg merge
- 7h 34m
- Merged PRs (30d)
- 26
Description
Hi there,
I'm running a public Nextcloud instance for a little community and currently facing a major issue when attempting to switch from the SAML plugin to OpenID Connect for authentication. I am using keycloak as Identity Provider. I dont think its a bug, but rather wrong configuration.
When I deactivate the SAML plugin and enable OpenID Connect, all existing users disappear from the Nextcloud instance. If I re-enable the SAML plugin, the users reappear. Here's what I've tried so far to troubleshoot and resolve the issue:
Mapping Consistency:
SAML was using the username attribute for mapping users.
For OpenID Connect, I configured the User ID Mapping to username as well.
On Keycloak, I created a mapper that outputs username as a token claim.
Database Checks:
I inspected the oc_accounts table in the Nextcloud database, which stores user data in the uid field.
The uid values correspond to the usernames used by SAML, so the issue doesn't seem to be related to the database itself.
Logs:
When OpenID Connect is enabled, users attempting to log in receive the error: Failed to provision user.
There are no specific hints in the nextcloud.log file pointing to a clear cause.
It seems like Nextcloud doesn't recognize the existing users when switching to OpenID Connect, even though the username mapping is identical across both plugins.
I also tried preferred_username in the plugin and created mapper to username from preferred_username for the claim token. It also didnt help. No old user created with the SAML Plugin are there when i deactivare the SAML Plugin for nextcloud.
My Questions:
Why do users disappear from the Nextcloud instance when switching from SAML to OpenID Connect?
Is there a way to safely migrate users between these two authentication plugins without losing access or data?
Are there additional steps required to make Nextcloud recognize the existing users after switching to OpenID Connect?
Thanks in advance for your help! If you need more details or logs, I'd be happy to provide them.
I am just a hobby admin and authentication flows and systems are hard for me to understand.
Best regards,
Wario
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the SAML and OpenID Connect user-ID mapping configuration, including the Keycloak username and preferred_username claims. Inspect the nextcloud.log entry for “Failed to provision user”; done means determining whether existing SAML user IDs can be recognized by OpenID Connect and documenting a safe migration or configuration path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100