Re: [Dhis2-devs] API not showing 401 Unauthorized error

Hi Morten, All of the information is provided in this thread. What both Ranga and I are saying is that when authenticating with basic authentication, and the authentication is not successful the following behavior is seen 1) In versions below 2.27 and below, a 401 response is sent from the

Re: [Dhis2-devs] API not showing 401 Unauthorized error

In what version did this return a 401? because that sounds like a bug to me.. if you give me the version number, I can have a look -- Morten Olav Hansen Senior Engineer, DHIS 2 University of Oslo http://www.dhis2.org On Tue, Apr 24, 2018 at 9:38 AM, Morten Olav Hansen wrote:

Re: [Dhis2-devs] API not showing 401 Unauthorized error

I'm not sure exactly what you mean Jason, this has been like this always? Are you saying this behavior has changed? because it should not have. To make the browser properly redirect to the login page, it needs to send a 302 to forward it. In 2.28 we introduced the X-Requested-With header which

Re: [Dhis2-devs] WEB API Error in DHIS2.30

Hi, Since 2.29, *trackedEntity* is renamed to be *trackedEntityType*. This is documented in our release note , please go through it especially the upgrade notes. If you are upgrading from an old version, you are supposed to run the upgrade script first. -- Abyot A.

Re: [Dhis2-devs] API not showing 401 Unauthorized error

Hi Bob, Yeah,I am not sure its fine either but what I am trying to get information on is what the expected behavior actually should be. Seems it should not be this though from what you and Ranga are saying. Just to exclude any possible effect from the reverse proxy, its the same against a

Re: [Dhis2-devs] WEB API Error in DHIS2.30

I found the problem The dhis2 documents is about version 2.26 which the class TrackedEntityInstance has an attribute named TrackedEntity. I think an documentation process is required for the new versions. regards On Sat, Apr 21, 2018 at 6:01 PM, mahdi asgari wrote: >

Re: [Dhis2-devs] API not showing 401 Unauthorized error

Hi Jason I am not sure that this is all fine. It looks to me like this is a bug which has slipped in and that the original 401 response is the correct expected behaviour. API users using pre-emptive basic authentication have no good reason to be redirected to the login page with invalid

Re: [Dhis2-devs] API not showing 401 Unauthorized error

Hi Morten, I am going to persist here, as its still not clear to me what has changed in the API. Ranga documents that the API behavior has changed when trying to access /api/me with basic authentication. It has changed from a 401 to a 302. This also breaks the API tests (

Re: [Dhis2-devs] [Dhis2-users] Android tracker enrollement

Hi Victor, as Knut said... it is not easy to understand your question. In case you mean "how can I DOWNLOAD all existing enrollments for an orgunit"? please try with the online search Icon (See image below). Best, Marta ​ On 21 April 2018 at 14:46, Knut Staring wrote: