Whitelist is configured correctly. After mounting document in chrome/edge, always on login page, cannot log in

Answer:

Without integration, high version chrome has cross-origin restrictions. You can use firefox to access, or configure nginx and then use chrome to access.

Nginx configuration (nginx.conf file content as follows, modify according to actual situation)

#user  nobody;
worker_processes  1;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid     logs/nginx.pid;

events {
   worker_connections  1024;
}

http {
   map $http_upgrade $connection_upgrade {
      default upgrade;
      ''    close;
  }
   include    mime.types;
   default_type  application/octet-stream;

  server {
    listen    8001;  
    ​     server_name  172.16.64.103;  
    location / {
        proxy_pass http://172.16.52.30:8001/;
        proxy_set_header Host $host; # pass the host header
        proxy_set_header Upgrade $http_upgrade; # allow websockets
        proxy_set_header Connection $connection_upgrade;
        proxy_set_header X-Real-IP $remote_addr; # Preserve client IP
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_http_version 1.1;
      }
   }
}

Configuration Description

Filez Document Platform is deployed at http://172.16.52.30:8001/, test page is deployed at http://172.16.64.103:8002/

Nginx listens on port 8001, which is the port where Filez Document Platform is located, and forwards to http://172.16.52.30:8001/, which is the address where Filez Document Platform is located.

When test page mounts Filez Document, replace the IP in the document address with the test page IP, i.e., replace http://172.16.52.30:8001/docs/app/local/752740ad-9417-45b2-a3bc-c116b179b08c/edit/content with http://172.16.64.103:8001/docs/app/local/752740ad-9417-45b2-a3bc-c116b179b08c/edit/content