IBM Sterling: Configurando comunicação TLS entre os componentes: Difference between revisions
No edit summary |
|||
| Line 53: | Line 53: | ||
[[Category:B2B Integrator]] | [[Category:B2B Integrator]] | ||
[[Category:SEAS]] | [[Category:SEAS]] | ||
[[Category:Sterling External Authentication Server]] | [[Category:Sterling External Authentication Server]] | ||
[[Category:SSP]] | [[Category:SSP]] | ||
[[Category:Sterling Secure Proxy]] | [[Category:Sterling Secure Proxy]] | ||
Revision as of 21:29, 2 November 2020
Criando as chaves
Quando criarmos as requisições de assinatura (CSR), você irá utilizar o artigo OpenSSL: Assinando um CSR com a nossa CA.
Configurando o IBM Sterling B2B Integrator para SSL
1) Ir para o diretório properties
cd /home/siuser/SI/properties
1) Editar o arquivo customer_overrides.properties e adicionar
noapp.HTTPS_REDIRECT_WARS=admin,dashboard,gbm,communitymanagement,myaft,portlets,filegateway,myfilegateway,myfg noapp.SKIP_BASEPORT_DEPLOYMENT_WARS=admin,dashboard,gpm,communitymanagement,myaft,portlets,filegateway,myfilegateway,myfg noapp.HTTPS_LIST_PORT=5001
Se quiser alterar o certificado também
noapp.sslCert=<CERTIFICADO_INTERNO_CRIADO>
Salvar o arquivo
2) Editar o arquivo sandbox.cfg e alterar
WEBAPP_LIST_PORT=5001 WEBAPP_PROTOCOL=https
Salvar o arquivo
3) Pare o B2Bi/SFG
4) Executar os commandos
cd /home/siuser/SI/bin ./setupfiles.sh ./deployer.sh
5) Inicie o B2Bi/SFG