Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
nextcloud/server#211 suggests that there could be a RESTful API for the clients to directly register in the client.
API flow that I can think of now:
A different API design is required considering admin approval #2
Would it make sense to reconsider the flow?
I do agree that admin approval might be important. But the greater goal for me would be to have a signup flow a la dropbox:
So this would be the API:
And then as a provider, I could redirect it to another backend like:
And then in term of flow, we could still do the following a posteriori:
And depending on these options, the server could return a response showed to the client.
I know it would require some changes to the current app. But in term of UX, this would be optimal IMHO.
I'll be working on implementing a provider list and optional registration feature on the Nextcloud client during this years google summer of code, so I'm willing to implement such an API and especially use the existing registration app for that. @pellaeon Would you be open to pull requests for that?
@pierreozoux That draft makes sense, especially auto discovery via .well-known path would be nice.
I've summarized both of your ideas to this rough API draft:
200 Signup successfull
200 if registration status is FINISHED
403 if email confirmation is still required
As an initial starting point i would add two possible states to the registration status:
Overview of the client procedure:
All endpoints the client interacts with have to be OCS endpoints.