user_external
user_external copied to clipboard
nextcloud
External auth via POST
Is your feature request related to a problem? Please describe. I have an external system to manage and authenticate users. I can't give nextcloud to this system, but I want to give users, managed by that system access to nextcloud.
Describe the solution you'd like Calling an API would be a solution to perform authentication. Nextcloud is just doing the communication to the API and provides a token, a username and a password. The system checks the provided data and sends a response if the authentication was successful or not. My idea: Nextcloud ---- POST DATA (token, user, pass) ----> domain.tld/auth.php ----> perform some checks ------ auth successful or not ---> Nextcloud
Additional context I would love to implement this feature, but before starting with the implementation, we should discuss whether we want to have this feature or not.
In general there is nothing that would speak against this...
What kind of external system to manage users/authentication would this be?
The auth.php, is it custom made by you? Would you provide an example somewhere for others to adapt?
What kind of external system to manage users/authentication would this be?
That's the point. I want to implement something that supports a self-developed authentication solution. So this authentication part is handled by something else, we're just checking if the external authentication endpoint says the user can access the cloud instance or not. Of course I can provide an example of this auth.php, but I don't want to establish a new authentication standard, I just want to allow very flexible external user access to the cloud without doing the authentication on nextcloud level. Just simply relying on a third-party authenticator/authentication.
okay, I see... yes I think it makes sense to have this in user_external... :)
Nice. I try to refine my code and will share it here to do a review.
Hi, i also need this functionality to nextcloud but i can see the issue was not closed and this development is not in master branch. Do you know when the issue is scheduled to close and merged to master?
Thank you!!
