Repository navigation
API for account registration #211
Description
Following a discussion about improving the setup screen for Android client, it would be nice to have an API for streamlined account registration, so that a new user can choose a provider in the the Android client's setup screen and directly register an account with that provider, from within the client. (Thunderbird and Pidgin for example offer the same in-app-account-registration feature for select email and XMPP providers, respectively.)
@jancborchardt @AndyScherzinger
Activity
MariusBluem commentedon Jun 23, 2016
Maybe we could integrate this one better:
https://github.com/pellaeon/registration
...but I have to say that I am not really convinced about this feature especially with the provider and android client aspect 😕
MorrisJobke commentedon Jun 24, 2016
This has nothing to do with LDAP ;)
In the past it was only referred to the registration app. Maybe we could somehow integrate this better as a possible capability and then let the android app detect if this is enabled and has proper endpoints?
cc @karlitschek @pellaeon
karlitschek commentedon Jun 24, 2016
interesting idea. not sure how this works in practice because the setup process might be totally different. tos, pricing model, verification,...
AndyScherzinger commentedon Jun 24, 2016
@mabkenar and @jancborchardt's point here is to lower the barrier especially when the Android app is the entry point and the user isn't really familiar with Nextcloud to provide an easy way to get all set.
There are probably three scenarios for a user:
I am with @karlitschek that this is a bit tricky for tos and pricing model, etc.
As stated in the Android issue we might be able to add a filter to the app for a defined nextcloud URL which contains the server address which would enable the Nextcloud Android app to process the URL string, open the login screen and prefill the URL. This way people could send out emails (maybe via Nextcloud) to a user, the user click on the link, chooses the Android app to open the link, types in username and password, and is all set.
mabkenar commentedon Jun 24, 2016
Ok I see the complexities involved. Currently there is not even a standard practice on the registration webpage among different providers. For example Wint.global uses this other domain for registration, and yet the actual server is on this domain. And oCloud.de uses this page for presenting different plans, and the server is on this username-dependent domain.
Given the above mess, even pre-filling the server name by sending a link does not help.
Therefore this API can be as minimal as "a standardized web address relative to the base server address" on which new users can register a new account. And we can make this an optional feature for providers if they want to participate. But I'm not sure if this is worth the effort.
If no other practical ideas come to mind, we can close this issue.
jancborchardt commentedon Jun 24, 2016
@karlitschek we talked about this in the past thought, you also being a proponent of having 3 (or so) providers listed in the log-in process of the apps (Android, iOS and desktop as well). To make this flow easy, we would need such a registration API.
cc @Gomez as he runs a provider and might give input on how difficult this is to do.
pellaeon commentedon Jun 27, 2016
I look forward to work together on this API, I have created an issue for it nextcloud/registration#41
Gomez commentedon Jun 27, 2016
With this approach a installed nextcloud is needed (with registration app). I more like the idea of this comment and an API to get a cloud created by a provider.
jancborchardt commentedon Jun 27, 2016
@Gomez as you are a provider, do you maybe want to draft such an API so we know what is needed?
Gomez commentedon Jun 28, 2016
Sure!
As a first version i would suggest to just post a email and cloud/login name to a custom url of a provider and show the response.
Would be good to join forces as a team and work on the parts. Who is interested?
jancborchardt commentedon Jun 28, 2016
@Gomez how should the password be chosen? Or is this best done by token based auth then? (Problem would be to then connect with other devices)
cc @LukasReschke regarding security aspects.
Gomez commentedon Jun 28, 2016
@jancborchardt Send to the email. It does not solve a instant cloud creation, its just a first step. We can go further from there.
rullzer commentedon Sep 4, 2016
I would strongly discourage getting this stuff into the core. I think that will be a nightmare security wise.
IF this is wanted I would propose the following:
pierreozoux commentedon Feb 25, 2017
Agree with @rullzer, @Gomez let's discuss about it in nextcloud/registration#41 (and sorry for the delay..)
I'm talking about it again, as we are again discussing about how to implement a SignUp screen for the Qt client.
MorrisJobke commentedon Apr 18, 2018
cc @skjnldsv
MorrisJobke commentedon Oct 29, 2018
@skjnldsv Isn't this done nowadays?
skjnldsv commentedon Oct 30, 2018
Yes on https://github.com/nextcloud/preferred_providers :)