| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
I didn't try to find which package introduced a BC (might be user-bundle
or jms serializer)
|
| |
|
|
| |
Also update tests urls
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
While creating a new user using the API, we also create a new client for the current user.
So the app which just create the user can use its newly created client to configure the app.
That new client is only return after creating the user.
When calling the endpoint /api/user to get user information, the new client information won’t be return.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
I've added a toggle feature (in internal settings) so that user api creation can be disabled while form registration still can be enabled.
Also, the /api/user endpoint shouldn't require authentication. Even if we check the authentication when sending a GET request, to retrieve current user information.
I've moved all the internal settings definition to config to avoid duplicated place to define them.
I don't know why we didn't did that earlier.
|
| |
|
|
|
|
| |
The only ugly things is how we handle error by generating the view and then parse the content to retrieve all errors…
Fix exposition fields in User entity
|
|
|
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
