topic Get RESTApi response in Alfresco Forum

Get RESTApi response

jackarnd — Tue, 30 May 2017 09:07:28 GMT

Hello,I'd like to parse a string given by : http://localhost:8080/alfresco/api/-default-/public/alfresco/versions/1/people but my code doesn't log in alfresco.Thus, I wrote this code in my custom share page:<p id="peoplelist"></p><script> var people = new XMLHttpRequest(); peop

Re: Get RESTApi response

mehe — Tue, 30 May 2017 16:53:56 GMT

Hi Jack,

I'm bit puzzled by the message about port 8081 but you could try to enable cors in the web.xm of alfresco like described in the configuration for the alfresco ng-components: alfresco-ng2-components/ALFRESCOCORS.md at master · Alfresco/alfresco-ng2-components · GitHub

Maybe this helps...

cu Martin

Re: Get RESTApi response

jackarnd — Wed, 31 May 2017 07:27:49 GMT

Hi !
The port 8081 is because I used Maven to create my Alfresco repository and Share too. So Alfresco is running on 8080 and Share on 8081. So I've looked into enabling CORS in an Alfresco repo generated by Maven previously but it doesn't really work I think, the web.xml aren't the same, when I add the lines missing to enable CORS it bugs the compilation and so on...
But since Share works properly during the normal use I don't think that the CORS are the problem ? I don't know..

Re: Get RESTApi response

mehe — Wed, 31 May 2017 19:16:00 GMT

...but you are starting the XMLHttprequest from the html page - that means from your browser - if I understood the problem.

There is also the enablecors platform module JAR (see the above link) - maybe you can include this to your repo...

Re: Get RESTApi response

jackarnd — Thu, 01 Jun 2017 07:37:12 GMT

Ok I've seen with someone how to enable CORS in project. So I added these lines into my Alfresco repo (and put the lines in the web.xml such as said in the github link, and added the jar wherever I could or seemed right aha) :

<dependency>
      <groupId>org.alfresco</groupId>
      <artifactId>enablecors</artifactId>
      <version>1.0</version>
</dependency>
<dependency>
      <groupId>com.thetransactioncompany</groupId>
      <artifactId>cors-filter</artifactId>
      <version>2.5</version>
</dependency>

But I still get the same problems..

I was also wondering since I'm creating a new page in Share do I have to add lines into the configurations xml files of this page to access the Alfresco database ? My xml files only contain :

The first one:

<page>
<template-instance>new-page</template-instance>
<authentication>none</authentication> 
</page>

The second one:

<template-instance>
<template-type>new-page/new-page</template-type>
</template-instance>

Re: Get RESTApi response

kevinr1 — Thu, 01 Jun 2017 09:17:38 GMT

The problem isn't related to CORS. You say "custom share page" - which means you should be calling all Alfresco APIs through the Share proxy to piggy-back onto the existing authentication that Share is already using. You are trying to call Alfresco server directly, which is a bad idea from Share - as you have no idea what authentication chain is being used etc.

To call that API through Share and get the result is simply a matter of changing the GET URL:

http://localhost:8081/share/proxy/alfresco-api/-default-/public/alfresco/versions/1/people

That will return the result you want, it will also use the existing authentication for the logged in Share user.

Cheers,

Kevin

Re: Get RESTApi response

jackarnd — Thu, 01 Jun 2017 15:32:15 GMT

Ok thank you a lot !! That works fine !

With gratitude,

Jack

Re: Get RESTApi response

jackarnd — Tue, 06 Jun 2017 13:29:36 GMT

I was wondering, I have an Apache2 server running on a Raspberry Pi, so I wanted to know if the same page I'm working on could work. But there is no share proxy. so I used the code I made at the beginning to access the api

people.open('GET', 'http://192.168.1.103:8080/alfresco/api/-default-/public/alfresco/versions/1/people', true, 'admin', 'admin');

But this doesn't work (as kinda expected).

So how am I supposed to access alfresco from another instance than Share ?

Keeping up,

Jack.