nextcloud / nextcloud/user_saml
API endpoint for user_saml to allow provisionning of SAML users
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
Hey, hello.
While creating a setup with a nextcloud instance with an SAML auth as single auth provider, we ran into a problem :
Any newly created in the IDP user are not visible in nextcloud, and are provisionned at the very first connection of the user on the platform.
There is already an API endpoint for creating nextcloud user but it works only for user that uses the basic nextcloud auth, not for the users that log in through SAML.
The firm I work for would like to add a provisioning SAML user API endpoint (in the exact same way it the createUserIfNotExists function do at first login).
It will be possible to provision user in the custom user_saml user table and allow the user to immediately exist in nextcloud without waiting to have him making his first log-on on the nextcloud instance.
If we add this API endpoint, would you be interested in accept such a merge request on the user_saml plugin? or should we develop a custom plugin (but that will more or less literally just re-use all the user_saml user creation process)?
Thanks,
Michel
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 reading the existing user-creation API and the user_saml createUserIfNotExists flow described in the issue. Define how an API request would provision a SAML user in the user_saml table and how completion would be verified, then confirm the maintainers accept this scope before implementing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100