{"id":6841,"date":"2019-06-14T15:59:57","date_gmt":"2019-06-14T18:59:57","guid":{"rendered":"https:\/\/kb.elipse.com.br\/?p=6841"},"modified":"2024-03-26T11:25:57","modified_gmt":"2024-03-26T14:25:57","slug":"seguranca-de-dados-do-epm-via-https","status":"publish","type":"post","link":"https:\/\/kb.elipse.com.br\/en\/seguranca-de-dados-do-epm-via-https\/","title":{"rendered":"Seguran\u00e7a de dados do EPM via HTTPS."},"content":{"rendered":"

Neste artigo, abordaremos como utilizar um servidor de Proxy para redirecionar todo o tr\u00e1fego de uma porta para os servidores do EPM Portal e EPM Web Server, e explicaremos como habilitar HTTPS<\/em> no\u00a0Proxy<\/em> e, desta forma, permitir a criptografia do tr\u00e1fego e uma conex\u00e3o segura.<\/p>\n

Neste ambiente, o Proxy<\/em> seria o ponto de acesso p\u00fablico e estaria na fronteira da infraestrutura de rede, enquanto que os servidores do EPM Portal e EPM Web Server estariam protegidos e com seu acesso externo bloqueado.<\/p>\n

Instala\u00e7\u00e3o do servidor\u00a0Proxy<\/em> (NGINX)<\/h2>\n

O primeiro item a ser configurado \u00e9 um servidor de\u00a0Proxy<\/em> reverso para conseguirmos redirecionar o tr\u00e1fego do EPM Portal e EPM Web Server.<\/p>\n

Existem algumas op\u00e7\u00f5es de produtos que permitem fazer este tipo de configura\u00e7\u00e3o, como o Apache<\/em>,\u00a0IIS<\/em>,\u00a0NGINX<\/em>, entre outros.<\/p>\n

Para o nosso caso, utilizaremos a vers\u00e3o gratuita mais recente do NGINX<\/em>, dispon\u00edvel para download em\u00a0https:\/\/nginx.org\/en\/download.html<\/a> no mesmo servidor onde est\u00e3o rodando o EPM Portal e o EPM Web Server.<\/p>\n

Ap\u00f3s o download, \u00e9 necess\u00e1rio apenas descompactar o arquivo em alguma pasta qualquer para que o NGINX possa ser considerado instalado.<\/p>\n

Feito isso, o conte\u00fado do diret\u00f3rio destino ser\u00e1 equivalente ao da imagem abaixo.<\/p>\n

\"Conte\u00fado
Conte\u00fado da pasta do NGINX<\/figcaption><\/figure>\n

Configura\u00e7\u00e3o do\u00a0Proxy<\/em> reverso (NGINX)<\/h2>\n

Ap\u00f3s a instala\u00e7\u00e3o, \u00e9 necess\u00e1rio configura o\u00a0Proxy<\/em> reverso do NGINX<\/em> para o redirecionamento do tr\u00e1fego.<\/p>\n

Para isso, \u00e9 necess\u00e1rio criar um arquivo de configura\u00e7\u00e3o do NGINX<\/em> em formato texto e com sintaxe pr\u00f3pria, conforme abaixo.<\/p>\n\n\n\n
\n
worker_processes\u00a0 1;\r\n\r\nevents {\r\n \u00a0\u00a0 worker_connections\u00a0 1024;\r\n}\r\n\r\nhttp {\r\n \u00a0\u00a0\u00a0\u00a0\u00a0 server {\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 listen 80<\/mark>;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 server_name\u00a0 [server_url]<\/mark>;\r\n\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_http_version 1.1;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_set_header\u00a0\u00a0 Upgrade $http_upgrade;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_set_header\u00a0\u00a0 Connection keep-alive;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_set_header\u00a0\u00a0 Host $host;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_set_header\u00a0\u00a0 X-Forwarded-For $proxy_add_x_forwarded_for;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_set_header\u00a0\u00a0 X-Forwarded-Proto $scheme;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_cache_bypass $http_upgrade;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 location \/auth {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_pass\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 http:\/\/localhost:44333<\/mark>;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }\r\n\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 location ~ ^\/(batch|epm|resource|opcua) {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_pass\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 http:\/\/localhost:44332<\/mark>;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }\r\n\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 location \/ {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_pass\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 http:\/\/localhost:44331<\/mark>;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }\r\n \u00a0\u00a0\u00a0\u00a0\u00a0 }\r\n}<\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Na configura\u00e7\u00e3o acima, o\u00a0NGINX<\/em> est\u00e1 configurado para receber conex\u00f5es pela porta 80, que \u00e9 a porta padr\u00e3o\u00a0HTTP<\/em>. Caso n\u00e3o seja poss\u00edvel utilizar esta porta, voc\u00ea pode alterar este par\u00e2metro conforme necess\u00e1rio.<\/p>\n
Em seguida, \u00e9 preciso alterar o par\u00e2metro\u00a0[server_url] <\/strong>para o endere\u00e7o que ser\u00e1 utilizado para acesso p\u00fablico ao EPM Portal. Por exemplo:<\/p>\n
portal.empresa.com.br<\/em><\/p>\n
Mais abaixo, \u00e9 poss\u00edvel verificar que h\u00e1 3 entradas separadas de location<\/em>. Estas entradas s\u00e3o respons\u00e1veis pelo redirecionamento do tr\u00e1fego para as portas correspondentes do EPM Portal e EPM Web Server.<\/p>\n
No nosso exemplo, os servi\u00e7os do EPM Portal e EPM Web Server (WebApi e Authentication) est\u00e3o configurados para receber conex\u00f5es pelas portas 44331, 44332 e 44333, respectivamente.<\/p>\n
\"EPM
EPM Portal Settings<\/figcaption><\/figure>\n
\n
\"EPM
EPM Web Server Settings<\/figcaption><\/figure>\n
Logo, caso alguma das portas n\u00e3o esteja de acordo com o que foi configurado no EPM Portal e EPM Web Server em sua m\u00e1quina, voc\u00ea precisar\u00e1 corrigir a configura\u00e7\u00e3o do NGINX<\/em> para indicar as portas corretas.<\/p>\n
Al\u00e9m disso, o NGINX<\/em> ser\u00e1 executado no mesmo servidor do EPM Portal e EPM Web Server, e por isso utilizamos localhost<\/em> nos endere\u00e7os.<\/p>\n
Agora, o servidor de\u00a0Proxy<\/em> reverso do\u00a0NGINX<\/em> est\u00e1 configurado corretamente. O pr\u00f3ximo passo \u00e9 inicializar o servi\u00e7o do\u00a0Proxy<\/em>.<\/p>\n
Inicializa\u00e7\u00e3o do\u00a0Proxy<\/em> reverso (NGINX)<\/h2>\n
Para executar o\u00a0NGINX<\/em> com o arquivo de configura\u00e7\u00e3o criado no passo anterior, devemos execut\u00e1-lo a partir de uma linha de comando com o par\u00e2metro -c<\/em><\/mark> e informando o caminho do arquivo, conforme abaixo:<\/p>\n
nginx.exe -c [caminho do arquivo de configura\u00e7\u00e3o]<\/em><\/mark><\/p>\n
\"Linha
Linha de comando do NGINX<\/figcaption><\/figure>\n
Ao executar este comando, o\u00a0NGINX<\/em> ser\u00e1 executado utilizando o arquivo de configura\u00e7\u00e3o passado e permanecer\u00e1 em execu\u00e7\u00e3o at\u00e9 que seja finalizado.<\/p>\n
Configura\u00e7\u00e3o do EPM Portal<\/h2>\n
Uma vez configurado o\u00a0Proxy<\/em> e com ele em execu\u00e7\u00e3o, \u00e9 necess\u00e1rio alterar os endere\u00e7os do WebApi e Authentication Endpoint que o EPM Portal utiliza para os endere\u00e7os p\u00fablicos do Proxy<\/em> e reiniciar o servi\u00e7o.<\/p>\n
\"EPM
EPM Portal Settings para HTTP<\/figcaption><\/figure>\n
Os novos valores s\u00e3o:<\/p>\n
    \n
  • WebApi Endpoint: http:\/\/portal.empresa.com.br<\/u><\/li>\n
  • Authentication Endpoint: http:\/\/portal.empresa.com.br<\/u><\/li>\n<\/ul>\n
    Configura\u00e7\u00e3o do EPM Web Server<\/h2>\n
    Como o servi\u00e7o do EPM Web Server n\u00e3o tem conhecimento da exist\u00eancia deste novo endere\u00e7o, ser\u00e1 necess\u00e1rio fazer algumas mudan\u00e7as na sua configura\u00e7\u00e3o.<\/p>\n
    Devemos habilitar a op\u00e7\u00e3o\u00a0Public Origin<\/em> e informar o endere\u00e7o p\u00fablico do\u00a0Proxy<\/em> para que seja exposto na web pelo servi\u00e7o de autentica\u00e7\u00e3o, al\u00e9m de incluir este mesmo endere\u00e7o na lista de endere\u00e7os aceitos pelo EPM Portal.<\/p>\n
    \"EPM
    EPM Web Server Settings para HTTP<\/figcaption><\/figure>\n
    Isto \u00e9 tudo o que precisa ser feito para rodar um\u00a0Proxy<\/em>, sem criptografia, com o EPM Portal e EPM Web Server.<\/p>\n
    A partir deste momento, j\u00e1 deve ser poss\u00edvel acessar o EPM Portal pelo endere\u00e7o p\u00fablico do\u00a0Proxy<\/em> (http:\/\/portal.empresa.com.br<\/u>).<\/p>\n
    Adicionando suporte a HTTPS<\/em> no Proxy<\/em><\/h2>\n
    Para adicionar suporte a\u00a0HTTPS<\/em> ao\u00a0Proxy<\/em> configurado anteriormente, ser\u00e1 necess\u00e1rio alterar o arquivo de configura\u00e7\u00e3o do\u00a0NGINX.<\/em><\/p>\n\n\n\n
    \n
    worker_processes\u00a0 1;\r\n\r\nevents {\r\n \u00a0\u00a0 worker_connections\u00a0 1024;\r\n}\r\n\r\nhttp {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 server {\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0listen 80;\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 return 301 https:\/\/$host$request_uri;\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/mark>\r\n\r\n \u00a0\u00a0\u00a0\u00a0\u00a0 server {\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 listen 443 ssl default_server;<\/mark>\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 server_name\u00a0 [server_url]<\/em>;\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0  ssl_certificate [path para certificate.crt];<\/em><\/mark>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ssl_certificate_key [path para certificate.key];<\/em><\/mark>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_http_version 1.1;\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_set_header\u00a0\u00a0 Upgrade $http_upgrade;\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_set_header\u00a0\u00a0 Connection keep-alive;\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_set_header\u00a0\u00a0 Host $host;\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_set_header\u00a0\u00a0 X-Forwarded-For $proxy_add_x_forwarded_for;\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_set_header\u00a0\u00a0 X-Forwarded-Proto $scheme;\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_cache_bypass $http_upgrade;\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 location \/auth {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_pass\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 http:\/\/localhost:44333;\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 location ~ ^\/(batch|epm|resource|opcua) {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_pass\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 http:\/\/localhost:44332;\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 location \/ {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 proxy_pass\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 http:\/\/localhost:44331;\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }\r\n}<\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
    Primeiro, alteramos a porta onde nosso servidor est\u00e1 escutando de 80 para 443, padr\u00e3o do\u00a0HTTPS.<\/em><\/p>\n
    listen 443;<\/mark><\/p>\n
    Em seguida, precisamos informar o caminho dos arquivos do certificado que estar\u00e3o associados a esta porta. Ambos os arquivos (certificado e sua chave) devem estar no formato PEM<\/strong>. Por exemplo:<\/p>\n
    ssl_certificate C:\/certs\/nginx.crt;<\/em>
    \nssl_certificate_key C:\/certs\/nginx.key;<\/em><\/mark><\/p>\n\n\n\n\n
    Nota<\/th>\n<\/tr>\n
    Para gerar um certificado auto assinado para testes, podemos usar a ferramenta por linha de comando OpenSSL<\/em><\/strong>. Criamos um arquivo de configura\u00e7\u00e3o com o conte\u00fado do anexo<\/strong> para a gera\u00e7\u00e3o do certificado usando o comando abaixo, modificando as partes destacadas conforme necess\u00e1rio. No exemplo abaixo, ssl.conf <\/em>\u00e9 o caminho para este arquivo.<\/p>\n
    openssl.exe req -x509 -nodes -days 365 -out nginx.crt -keyout nginx.key -extensions v3_req -config ssl.conf<\/mark><\/em><\/p>\n
    Este comando ir\u00e1 gerar dois arquivos, nginx.crt<\/em> e nginx.key<\/em>, que podem ser utilizados diretamente no arquivo de configura\u00e7\u00e3o do nginx<\/em>. As m\u00e1quinas clientes<\/em> devem confiar no certificado gerado para que o HTTPS funcione de forma v\u00e1lida pelo navegador.<\/p>\n
    No entanto,\u00a0 este tipo de certificado n\u00e3o deve ser utilizado em produ\u00e7\u00e3o<\/em>. Em vez dele, deve ser usado um certificado verificado e validado por um autoridade certificadora (CA) ra\u00edz confi\u00e1vel.<\/span><\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
    Atualizando a configura\u00e7\u00e3o do EPM Web Server para HTTPS<\/h2>\n
    Agora, \u00e9 preciso atualizar os valores da configura\u00e7\u00e3o do EPM Web Server para que ele passe a usar o endere\u00e7o HTTPS,<\/em> e ent\u00e3o reiniciar o servi\u00e7o.<\/p>\n
    \"EPM
    EPM Portal Settings para HTTPS<\/figcaption><\/figure>\n
    Os novos valores s\u00e3o:<\/p>\n
      \n
    • EPM Portal redirects:\u00a0https:\/\/portal.empresa.com.br<\/span><\/li>\n
    • Public Origin:\u00a0https:\/\/portal.empresa.com.br<\/li>\n<\/ul>\n
      Atualizando a configura\u00e7\u00e3o do EPM Portal para HTTPS<\/h2>\n
      Em seguida, devemos atualizar a configura\u00e7\u00e3o do EPM Portal para utilizar o endere\u00e7o HTTPS<\/em> e reiniciar o servi\u00e7o.<\/p>\n
      \"EPM
      EPM Portal Settings para HTTPS<\/figcaption><\/figure>\n
      Os novos valores s\u00e3o:<\/p>\n
        \n
      • WebApi Endpoint: https:\/\/portal.empresa.com.br<\/span><\/li>\n
      • Authentication Endpoint:\u00a0https:\/\/portal.empresa.com.br\/auth<\/span><\/li>\n<\/ul>\n
        A partir deste momento, o EPM Portal j\u00e1 deve estar funcionando corretamente no endere\u00e7o\u00a0HTTPS<\/em>, porta 443. Al\u00e9m disso, no arquivo de configura\u00e7\u00e3o do\u00a0NGINX<\/em>, adicionamos um redirecionamento autom\u00e1tico da porta 80 para a 443.<\/p>\n
         \u00a0\u00a0\u00a0\u00a0\u00a0 server {<\/mark>
        \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0listen 80;<\/mark>
        \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 return 301 https:\/\/$host$request_uri;<\/mark>
        \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }
        \n<\/mark><\/p>\n
        Dessa forma, podemos conectar ao EPM Portal diretamente por\u00a0HTTPS <\/em>pela porta 443; alternativamente, ao conectar por HTTP<\/em> pela porta 80, seremos redirecionados para a porta 443 (HTTPS<\/em>).<\/p>\n
        Anexo<\/h2>\n
        Exemplo de conte\u00fado do arquivo de configura\u00e7\u00e3o para gera\u00e7\u00e3o do certificado auto-assinado.<\/p>\n\n\n\n
        \n
        [req]\r\ndefault_bits = 2048\r\nprompt = yes\r\ndefault_md = sha256\r\nreq_extensions = v3_req\r\ndistinguished_name = req_distinguished_name\r\n\r\n[ req_distinguished_name ]\r\ncountryName\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = Country Name (2 letter code)\r\ncountryName_default\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = BR<\/mark>\r\nstateOrProvinceName\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = State or Province Name (full name)\r\nstateOrProvinceName_default = Rio Grande do Sul<\/mark>\r\nlocalityName\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = Locality Name (eg, city)\r\nlocalityName_default\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = Porto Alegre<\/mark>\r\norganizationName\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = Organization Name (eg, company)\r\norganizationName_default\u00a0\u00a0\u00a0 = Elipse Software<\/mark>\r\ncommonName\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = Common Name (e.g. server FQDN or YOUR name)\r\ncommonName_max\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = 64\r\ncommonName_default\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = portal.empresa.com.br<\/mark>\r\n\r\n[ v3_req ]\r\nsubjectAltName = @alt_names\r\n\r\n[ alt_names ]\r\nDNS.1 = portal.empresa.com.br<\/mark><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"
        Neste artigo, abordaremos como utilizar um servidor de Proxy para redirecionar todo o tr\u00e1fego de uma porta para os servidores do EPM Portal e EPM Web Server, e explicaremos como…<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0},"categories":[676],"tags":[867,866,869,870,868,863,871,872,865,864],"yoast_head":"\nSeguran\u00e7a de dados do EPM via HTTPS. - Elipse Knowledgebase<\/title>\n<meta name=\"description\" content=\"Como utilizar HTTPS na conex\u00e3o com o EPM Portal e tamb\u00e9m com o EPM Processor utilizando o NGINX como servidor Proxy, redirecionando o tr\u00e1fego da porta 80.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"EPM na web via HTTPS\" \/>\n<meta property=\"og:description\" content=\"Como utilizar HTTPS na conex\u00e3o com o EPM Portal e tamb\u00e9m com o EPM Processor utilizando o NGINX como servidor Proxy, redirecionando o tr\u00e1fego da porta 80.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/\" \/>\n<meta property=\"og:site_name\" content=\"Elipse Knowledgebase\" \/>\n<meta property=\"article:publisher\" content=\"http:\/\/www.facebook.com\/elipsesoftware\" \/>\n<meta property=\"article:published_time\" content=\"2019-06-14T18:59:57+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-03-26T14:25:57+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/06\/6841\/img1.png\" \/>\n<meta name=\"author\" content=\"Daniel Seibel Silva\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"Dados do EPM na web via HTTPS\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Seibel Silva\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/\"},\"author\":{\"name\":\"Daniel Seibel Silva\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/person\/c8f79a90ce0cbb19f4d1c1cdfacdbbc5\"},\"headline\":\"Seguran\u00e7a de dados do EPM via HTTPS.\",\"datePublished\":\"2019-06-14T18:59:57+00:00\",\"dateModified\":\"2024-03-26T14:25:57+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/\"},\"wordCount\":2537,\"commentCount\":1,\"publisher\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#organization\"},\"keywords\":[\"certificado\",\"criptografia\",\"EPM Portal\",\"EPM Processor\",\"EPM Web Server\",\"https\",\"NGINX\",\"Proxy\",\"seguran\u00e7a de dados\",\"SSL\/TLS\"],\"articleSection\":[\"Elipse Plant Manager\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/\",\"url\":\"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/\",\"name\":\"[:pt]Seguran\u00e7a de dados do EPM via HTTPS.[:en]Seguran\u00e7a de dados do EPM via HTTPS.[:] - Elipse Knowledgebase\",\"isPartOf\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#website\"},\"datePublished\":\"2019-06-14T18:59:57+00:00\",\"dateModified\":\"2024-03-26T14:25:57+00:00\",\"description\":\"Como utilizar HTTPS na conex\u00e3o com o EPM Portal e tamb\u00e9m com o EPM Processor utilizando o NGINX como servidor Proxy, redirecionando o tr\u00e1fego da porta 80.\",\"breadcrumb\":{\"@id\":\"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"In\u00edcio\",\"item\":\"https:\/\/kb.elipse.com.br\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Seguran\u00e7a de dados do EPM via HTTPS.\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/kb.elipse.com.br\/#website\",\"url\":\"https:\/\/kb.elipse.com.br\/\",\"name\":\"Elipse Knowledgebase\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/kb.elipse.com.br\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/kb.elipse.com.br\/#organization\",\"name\":\"Elipse Software\",\"url\":\"https:\/\/kb.elipse.com.br\/\",\"sameAs\":[\"http:\/\/www.facebook.com\/elipsesoftware\"],\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png\",\"contentUrl\":\"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png\",\"width\":161,\"height\":58,\"caption\":\"Elipse Software\"},\"image\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/person\/c8f79a90ce0cbb19f4d1c1cdfacdbbc5\",\"name\":\"Daniel Seibel Silva\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/3f74c491a22a7f66a9ab79f1826a1939?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/3f74c491a22a7f66a9ab79f1826a1939?s=96&d=mm&r=g\",\"caption\":\"Daniel Seibel Silva\"},\"url\":\"https:\/\/kb.elipse.com.br\/en\/author\/daniel\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Seguran\u00e7a de dados do EPM via HTTPS. - Elipse Knowledgebase","description":"Como utilizar HTTPS na conex\u00e3o com o EPM Portal e tamb\u00e9m com o EPM Processor utilizando o NGINX como servidor Proxy, redirecionando o tr\u00e1fego da porta 80.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/","og_locale":"en_US","og_type":"article","og_title":"EPM na web via HTTPS","og_description":"Como utilizar HTTPS na conex\u00e3o com o EPM Portal e tamb\u00e9m com o EPM Processor utilizando o NGINX como servidor Proxy, redirecionando o tr\u00e1fego da porta 80.","og_url":"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/","og_site_name":"Elipse Knowledgebase","article_publisher":"http:\/\/www.facebook.com\/elipsesoftware","article_published_time":"2019-06-14T18:59:57+00:00","article_modified_time":"2024-03-26T14:25:57+00:00","og_image":[{"url":"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/06\/6841\/img1.png"}],"author":"Daniel Seibel Silva","twitter_card":"summary_large_image","twitter_title":"Dados do EPM na web via HTTPS","twitter_misc":{"Written by":"Daniel Seibel Silva","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/#article","isPartOf":{"@id":"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/"},"author":{"name":"Daniel Seibel Silva","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/person\/c8f79a90ce0cbb19f4d1c1cdfacdbbc5"},"headline":"Seguran\u00e7a de dados do EPM via HTTPS.","datePublished":"2019-06-14T18:59:57+00:00","dateModified":"2024-03-26T14:25:57+00:00","mainEntityOfPage":{"@id":"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/"},"wordCount":2537,"commentCount":1,"publisher":{"@id":"https:\/\/kb.elipse.com.br\/#organization"},"keywords":["certificado","criptografia","EPM Portal","EPM Processor","EPM Web Server","https","NGINX","Proxy","seguran\u00e7a de dados","SSL\/TLS"],"articleSection":["Elipse Plant Manager"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/","url":"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/","name":"[:pt]Seguran\u00e7a de dados do EPM via HTTPS.[:en]Seguran\u00e7a de dados do EPM via HTTPS.[:] - Elipse Knowledgebase","isPartOf":{"@id":"https:\/\/kb.elipse.com.br\/#website"},"datePublished":"2019-06-14T18:59:57+00:00","dateModified":"2024-03-26T14:25:57+00:00","description":"Como utilizar HTTPS na conex\u00e3o com o EPM Portal e tamb\u00e9m com o EPM Processor utilizando o NGINX como servidor Proxy, redirecionando o tr\u00e1fego da porta 80.","breadcrumb":{"@id":"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/kb.elipse.com.br\/seguranca-de-dados-do-epm-via-https\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"In\u00edcio","item":"https:\/\/kb.elipse.com.br\/en\/"},{"@type":"ListItem","position":2,"name":"Seguran\u00e7a de dados do EPM via HTTPS."}]},{"@type":"WebSite","@id":"https:\/\/kb.elipse.com.br\/#website","url":"https:\/\/kb.elipse.com.br\/","name":"Elipse Knowledgebase","description":"","publisher":{"@id":"https:\/\/kb.elipse.com.br\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/kb.elipse.com.br\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/kb.elipse.com.br\/#organization","name":"Elipse Software","url":"https:\/\/kb.elipse.com.br\/","sameAs":["http:\/\/www.facebook.com\/elipsesoftware"],"logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/","url":"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png","contentUrl":"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png","width":161,"height":58,"caption":"Elipse Software"},"image":{"@id":"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/person\/c8f79a90ce0cbb19f4d1c1cdfacdbbc5","name":"Daniel Seibel Silva","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3f74c491a22a7f66a9ab79f1826a1939?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3f74c491a22a7f66a9ab79f1826a1939?s=96&d=mm&r=g","caption":"Daniel Seibel Silva"},"url":"https:\/\/kb.elipse.com.br\/en\/author\/daniel\/"}]}},"_links":{"self":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts\/6841"}],"collection":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/comments?post=6841"}],"version-history":[{"count":29,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts\/6841\/revisions"}],"predecessor-version":[{"id":16096,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts\/6841\/revisions\/16096"}],"wp:attachment":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/media?parent=6841"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/categories?post=6841"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/tags?post=6841"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}