topic Re: adf-viewer causes 401 after deploy in Alfresco Forum

adf-viewer causes 401 after deploy

d_moeyersons — Mon, 17 Sep 2018 10:13:41 GMT

When I deploy my app to my webserver (Tomcat v7.0.59) when I try to preview any document (with adf-viewer), the document viewer doesn't show it and the console log shows a 401 error like this:GET https://o-alfresco.vmm.be/alfresco/api/-default-/public/alfresco/versions/1/nodes/5c62ee00-6a32-4406-a51

Re: adf-viewer causes 401 after deploy

dvuika — Mon, 17 Sep 2018 13:13:24 GMT

Can you please provide any extra details, i.e. what are the browser error details in the Network tab. The stack traces if there's a JS error during that call, etc.

Re: adf-viewer causes 401 after deploy

d_moeyersons — Mon, 17 Sep 2018 13:40:38 GMT

Details

Network tab capture

Request URL: https://o-alfresco.vmm.be/alfresco/api/-default-/public/alfresco/versions/1/nodes/1370f78d-0eb0-4ddf-bfdf-69be0803eb67/renditions/pdf/content?attachment=false&alf_ticket=TICKET_994a22cb59b72a8a5849bb88b051256b12d21643
Request Method: GET
Status Code: 401 Unauthorized
Remote Address: 192.168.130.117:443
Referrer Policy: no-referrer-when-downgrade
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin: https://o-dms.vmm.be
Content-Length: 360
Content-Type: text/html;charset=UTF-8
Date: Mon, 17 Sep 2018 13:24:27 GMT
Server: webserver
Set-Cookie: JSESSIONID=B35178E11C94A8CE9C8E75181863F001; Path=/alfresco/; HttpOnly
Vary: Origin
WWW-Authenticate: Negotiate
Accept: */*
Accept-Encoding: gzip, deflate, br
Accept-Language: nl-NL,nl;q=0.9,en-US;q=0.8,en;q=0.7
Connection: keep-alive
Host: o-alfresco.vmm.be
Origin: https://o-dms.vmm.be
Referer: https://o-dms.vmm.be/dms/vergadersite/vgd-test-vergadersite/vergadering/be6c3e3d-58d1-4629-b838-6601754959d4/verslag-bekijken/1370f78d-0eb0-4ddf-bfdf-69be0803eb67
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
attachment: false
alf_ticket: TICKET_994a22cb59b72a8a5849bb88b051256b12d21643

There are no js errors.

Re: adf-viewer causes 401 after deploy

dvuika — Mon, 17 Sep 2018 13:44:01 GMT

Have you tried same request with Postman? to check if your Tomcat is correctly configured and URL indeed works?

Re: adf-viewer causes 401 after deploy

d_moeyersons — Mon, 17 Sep 2018 13:54:17 GMT

Hi Denys,

I tried it now. The request works fine with Postman. I get a pdf with the content of the document.

Re: adf-viewer causes 401 after deploy

eugenio_romano — Tue, 18 Sep 2018 10:05:12 GMT

it looks like your configuration issue in tomcat could you maybe try to follow this guide :

Enabling CORS in Apache

Re: adf-viewer causes 401 after deploy

d_moeyersons — Tue, 18 Sep 2018 11:27:26 GMT

Hi Eugenio,

I have tried this implementation that you mention before, both globally as wel as in the webapp, I have never gotten it working with Alfresco.

I currently use the CORS implementation that is commented out in the alfresco.war\WEB-INF\web.xml . It works fine. And there is no reason that it shouldn't work with the document viewer.
Also if there are CORS error: the console messages should mention it, it doesn't. And CORS is disabled in my Internet Explorer and MS Edge, and it also fails there, this is no CORS problem.

David.

Re: adf-viewer causes 401 after deploy

d_moeyersons — Thu, 20 Sep 2018 13:28:25 GMT

I also tried it in Apache HTTP server, I got exactly the same error.

There is a difference between the call that causes 401 and the other calls.
CORS is active, the headers are returned (as you can see in the logs), so that is not the problem & CORS doesn't trigger 401.
But there is no Authorization header, instead a alf_ticket is added. Why is that?

David.

Re: adf-viewer causes 401 after deploy

eugenio_romano — Mon, 24 Sep 2018 14:06:42 GMT

Sorry but I am not able to replicate this problem it could be maybe simple if you provide something to try

Re: adf-viewer causes 401 after deploy

d_moeyersons — Tue, 25 Sep 2018 07:10:16 GMT

Hi Eugenio,

I did some more tests today, I only get the error because my Alfresco server and ADF app are on different servers.

(ADF runs on the same server as the share environment - We have one server for the database Postgres, one server for the Alfresco platform environment, one server for the Share and ADF environment)

When I upload the ADF app to the Alfresco platform (back-end) server, I get no errors.

I also checked the Alfresco logs for csrf errors when the 401 error shows up, i get no such errors.

Have you tried both the Alfresco platform server and the ADF client on one server, or have you tried it on different servers?
My current ADF app is created for a customized Alfresco server, it has several Java extensions especially made for our organisation, it won't work well on a standard Alfresco setup. But I get the same errors with the ADF demo application: alfresco-ng2-components/demo-shell at master · Alfresco/alfresco-ng2-components · GitHub

Let me know if that is enough or you need more information.

Thanks!

David.

Re: adf-viewer causes 401 after deploy

dvuika — Tue, 25 Sep 2018 08:14:30 GMT

We use ADF apps internally with different servers and have not had any issues so far. I'm afraid we still need steps to reproduce it.

Can you try to replicate the issue with Alfresco Content Application? GitHub - Alfresco/alfresco-content-app: Alfresco Example Content Application

We don't support demo shell, so please also consider using Yeoman generator to create a fresh app and document steps to reproduce the problem (ADF 2.5.0 and ACS 5.2.3 or 6.0.x)

Re: adf-viewer causes 401 after deploy

eugenio_romano — Tue, 25 Sep 2018 09:14:03 GMT

Hi, David has Denys says we run different apps more than once a day with more than 700 e2e test that target also the viewer.

So far those apps are no highlighting any of your problems.

I also checked it manually on the server and they are working fine .

It is for sure your local configuration problem. My suggestion as Denys sasys is recreating a sandbox example with your configuration starting maybe from the example content app.

If you can recreate this error in a sandbox app that I can try exaplaing the step I guess we can help you better

Re: adf-viewer causes 401 after deploy

d_moeyersons — Tue, 25 Sep 2018 10:38:15 GMT

Hi,

As Denys recommended, I downloaded the Alfresco Content Application: GitHub - Alfresco/alfresco-content-app: Alfresco Example Content Application. I am using ACS 5.2.3.

These were the steps:

Unpack alfresco-content-app-master.zip
Edit /proxy.conf.js and change the following values:

proxy.conf.js
"target": "https://o-alfresco.vmm.be", "secure": true,

Run: npm install
Run: npm start
Open http://localhost:4200/
Open a document preview

--> the document preview works correctly

Edit /package.json and change the following value:

package.json
"build": "npm run server-versions && npm run build.libs.prod && node --max-old-space-size=8192 node_modules/@angular/cli/bin/ng build app --prod --base-href /test/",

Run: npm run build
Edit /dist/app/app.config.json and change the following value:

app.config.json
"ecmHost": "https://o-alfresco.vmm.be",

Create the file: /dist/app/WEB-INF/web.xml with the following content:

web.xml
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0" metadata-complete="true"> <display-name>ADF Test</display-name> <description> ADF Test </description> <error-page> <error-code>404</error-code> <location>/index.html</location> </error-page> </web-app>

web.xml

<web-app xmlns="http://java.sun.com/xml/ns/javaee"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
        http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
   version="3.0"
   metadata-complete="true">

   <display-name>ADF Test</display-name>
   <description>
  ADF Test
   </description>

   <error-page>
  <error-code>404</error-code>
  <location>/index.html</location>
   </error-page>
</web-app>

Upload /dist/app/ content to Tomcat server (https://o-dms.vmm.be/test)
Start the server
Navigate to https://o-dms.vmm.be/test
Open a document preview

--> 401 on opening a document preview

Re: adf-viewer causes 401 after deploy

dvuika — Tue, 25 Sep 2018 12:22:43 GMT

Thanks for the details. We will try to reproduce it locally.

Meanwhile, could you please test the configuration where base href is "./" ?

npm run build -- --base-href ./‍

Thanks.

Re: adf-viewer causes 401 after deploy

d_moeyersons — Tue, 25 Sep 2018 13:11:28 GMT

Same result with --base-href ./

Re: adf-viewer causes 401 after deploy

dvuika — Thu, 27 Sep 2018 13:42:00 GMT

Maybe you could also see if you can reproduce that using ACS 6 and Tomcat 8?

Re: adf-viewer causes 401 after deploy

d_moeyersons — Fri, 28 Sep 2018 09:34:09 GMT

Hi Denys,

The 401 error doesn't come up with ACS 6 & Tomcat 8, the preview is shown.
It would be nice for us if ACS 5.2.3 would work too. We currently have a few reasons not to upgrade to ACS 6.

David.

Re: adf-viewer causes 401 after deploy

dvuika — Fri, 28 Sep 2018 09:47:42 GMT

Good to hear that ACS 6 is working. You can also verify you have everything configured for the old tomcat version (Angular Docs) and create a support ticket to get it sorted out for 5.2.3 and tomcat 7