Is your feature request related to a problem? Please describe.
As part of the completion of user signup, and our use of Auth0, currently the backend user (auth0user) is being created through a database migration, this isn't good. We need an effective way of allowing Auth0 to populate the backend with newly registered users, so that people can login to their own entity, not a centralised god entity.
Describe the solution you'd like
After creating the User Model in #10, we will need an authenticated view that can accept POST requests that will create a user with the parameters passed to it, this will consist of an addition in the form of a views.py file in the User application.
Describe alternatives you've considered
None.
Additional context
The view must authenticate with Auth0, and have adequate access control around it, as it will not be a user facing API, it will be entirely a management API, designed with the "sole" intention of populating the application with new users.
Is your feature request related to a problem? Please describe. As part of the completion of user signup, and our use of Auth0, currently the backend user (auth0user) is being created through a database migration, this isn't good. We need an effective way of allowing Auth0 to populate the backend with newly registered users, so that people can login to their own entity, not a centralised god entity.
Describe the solution you'd like After creating the User Model in #10, we will need an authenticated view that can accept POST requests that will create a user with the parameters passed to it, this will consist of an addition in the form of a
views.pyfile in theUserapplication.Describe alternatives you've considered None.
Additional context The view must authenticate with Auth0, and have adequate access control around it, as it will not be a user facing API, it will be entirely a management API, designed with the "sole" intention of populating the application with new users.
Definition of Done: