Re: [Dhis2-users] [Dhis2-devs] signing up for google earth engine for dhis

I have updated the tutorial now. Lars On Sun, Aug 7, 2016 at 1:59 PM, Bjørn Sandvik wrote: > Hi Calle, > > Yes, you need to attach the service account to a project - we will update > the documentation about this. > > If you already have a Google account, click on this link: >

Re: [Dhis2-users] [Dhis2-devs] DHIS2 based App http.post and put (403 error)

Hey Michael, Are you developing the app using CORS? If you're doing CORS requests you will need to include the header yes. If your app is running from within the dhis2 context (as in you installed it) you won't need to do so. Generally when the Authorization header is not send the API would 302

Re: [Dhis2-users] [Dhis2-devs] DHIS2 based App http.post and put (403 error)

Hi Mark, The app I am developing is running with-in a DHIS2 context. Below is the error from the console. I have also included the code fragment causing the error. [image: Inline images 1] var data = { "dashlets" : dashlets }

Re: [Dhis2-users] [Dhis2-devs] signing up for google earth engine for dhis

Hi Calle, Yes, you need to attach the service account to a project - we will update the documentation about this. If you already have a Google account, click on this link: https://console.developers.google.com/iam-admin/projects Click on "Create project" and name the project. When the project

Re: [Dhis2-users] [Dhis2-devs] signing up for google earth engine for dhis

Lars, Your step-by-step description don't fit what I get for Step 3 onwards - I see not "Create account' etc, just "Create project" and then it deviates completely from there. Regards calle On 6 August 2016 at 19:32, Lars Helge Øverland wrote: > Hi all, > > in DHIS 2.24 we

[Dhis2-users] DHIS2 based App http.post and put (403 error)

Hi, I am developing a DHIS2 based app using AngularJS. The $http.get is successful but I am getting 403 (Forbidden) with the POST and PUT when I try to add a new item to the dataStore. Am I supposed to include Authorization: Basic base64encode(username:password) in the header as well? Is there an