-
Notifications
You must be signed in to change notification settings - Fork 15
Expose the authenticated_userid in an endpoint #319
Conversation
Also now that the creator have got an automatic write access it is a bit less urgent. |
I propose to add a |
r? @n1k0 @leplatrem |
I remember that @ametaireau did not agree with that, since the hello endpoint does not require authentication... |
Note that with this PR the hello endpoint doesn't require authentication. It is just that if you need a userid you will provide a user Authentication. |
c1b1493
to
57725d3
Compare
I will merge for now and ask @ametaireau when he comes back and we can change the behaviour before the next release if necessary. The reason why I think this is a good and acceptable solution:
|
Expose the authenticated_userid in an endpoint
Lagguy r+ |
I don't understand why we were in a hurry for this... |
We are not. |
Add hoodie to the other solutions comparison matrix (fixes #282)
Clients need to know what's their userid is, in order to set and manage permission.
We should expose that in either an extra endpoint or the root one.
We may use the same endpoint as #318 in case we decide to create one.