You probably want to use the name me instead of currentUser as it’ the new name for it (and has been for a while, just being aliased to `currentUser``
In 224 we included a new me endpoint, which can now be reached at /api/24/me and /api/25/me
There seems to be a bug here though, that new endpoint should also be available at /api/me (and not /api/currentUser)
That said, the new endpoint is a bit different. What are you using this endpoint for? is it just to get info about current user, or is it to use some of its other capabilities ? like data set, program availability (/api/23/currentUser/programs/api/23/currentUser/dataSet)
···
On Tue, Oct 18, 2016 at 10:46 PM, Lorill Crees lcrees@2paths.com wrote:
Hi,
We are using 2.24 revision e2f8d0e and the endpoint /api/24/currentUser is not available. However, these two endpoints are available:
/api/currentUser
/api/23/currentUser
Is it possible to add the endpoint /api/24/currentUser, or is there a reason it is missing?
Thanks for this. We are getting the user roles from the user credentials, and I’ve confirmed this is available under /api/me and /api/24/me.
Thanks,
Lorill
···
On Sun, Oct 23, 2016 at 7:49 PM, Morten Olav Hansen morten@dhis2.org wrote:
Hi Lorill
So there’s a couple of things to note here:
You probably want to use the name me instead of currentUser as it’ the new name for it (and has been for a while, just being aliased to `currentUser``
In 224 we included a new me endpoint, which can now be reached at /api/24/me and /api/25/me
There seems to be a bug here though, that new endpoint should also be available at /api/me (and not /api/currentUser)
That said, the new endpoint is a bit different. What are you using this endpoint for? is it just to get info about current user, or is it to use some of its other capabilities ? like data set, program availability (/api/23/currentUser/programs/api/23/currentUser/dataSet)