How do you configure Stat Web Client to use HTTPS?
N/A
The Java Developer's Kit includes a utility to create certificates. Go to a command line and navigate to your JRE directory where keytool.exe is located. Type the following command:
keytool -genkey -alias key4stat -keyalg RSA -keystore key4stat.jks -keysize 2048 -validity 3650
This command tells Java to generate a self-signed certificate. Some prompts look like this:
Following the Warning, we execute the command suggested to migrate from JKS to PKCS12 format:
keytool -importkeystore -srckeystore key4stat.jks -destkeystore key4stat.jks -deststoretype pkcs12
Notice that there are two prompts for the password. That's because there's one password for the keystore and one password for the actual key. Test this using the defaults indicated above and also using something different for the password
By default, the keytool puts information in the "C:\Users\graiano" directory for your USER-ID. In the example above, we'd find that the keystore has been created as a file called:
C:\Users\graiano\key4stat.jks
<security-realm name="SslRealm">
<server-identities>
<ssl>
<keystore keystore-password="changeme" path="key4stat.jks" relative-to="jboss.server.config.dir" alias="key4stat"/>
</ssl>
</server-identities>
</security-realm>
set SERVER_CONFIG=standalone-full-https.xml
3. Additional steps for the EBS environment
Now we have the .jks and the .crt files created on the SCA machine, and we have to move to the EBS machine by FTP under the STAT_JAVA_HOME/jre/lib/security.
Using the keytool utility, we can import the certificate as below:
keytool -import -keystore jssecacerts -file Gio.crt -alias key4stat
Go into the OA_HOME\conf and edit the stat.conf setting the parameter below:
stat.central_agent.name_port:8443
stat.central_agent.protocol:https
Start the OA that will get an HTTPS communication with the SCA.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center