This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
wildfly [2020/07/23 12:00] mstraub [Deployment Timeout] |
wildfly [2020/10/08 16:04] mstraub [HTTPS & TLS Certificate] |
||
---|---|---|---|
Line 16: | Line 16: | ||
sudo chown --no-dereference wildfly:wildfly /opt/wildfly | sudo chown --no-dereference wildfly:wildfly /opt/wildfly | ||
sudo chown -HR wildfly:wildfly /opt/wildfly | sudo chown -HR wildfly:wildfly /opt/wildfly | ||
+ | </code> | ||
+ | |||
+ | Create a management user | ||
+ | <code bash> | ||
+ | sudo -u wildfly /opt/wildfly/bin/add-user.sh | ||
</code> | </code> | ||
Line 22: | Line 27: | ||
sudo -u wildfly /opt/wildfly/bin/standalone.sh | sudo -u wildfly /opt/wildfly/bin/standalone.sh | ||
</code> | </code> | ||
+ | |||
+ | Visit the managment console: https://localhost:9990 | ||
Line 187: | Line 194: | ||
When using HTTPS you should most probably also provide a valid [[https://de.wikipedia.org/wiki/Transport_Layer_Security|TLS]] (aka SSL) certificate. Otherwise browsers tend to block access to your page or at least give a big warning that the page is not secure. | When using HTTPS you should most probably also provide a valid [[https://de.wikipedia.org/wiki/Transport_Layer_Security|TLS]] (aka SSL) certificate. Otherwise browsers tend to block access to your page or at least give a big warning that the page is not secure. | ||
+ | |||
+ | FIXME explore: there seems to be a new way to configure Letsencrypt directly via the WildFly CLI since WildFly 14: https://developer.jboss.org/people/fjuma/blog/2018/08/31/obtaining-certificates-from-lets-encrypt-using-the-wildfly-cli | ||
The certificate must be present in a Java Keystore file. Copy ''com.example.jks'' to ''/opt/wildfly/standalone/configuration''. | The certificate must be present in a Java Keystore file. Copy ''com.example.jks'' to ''/opt/wildfly/standalone/configuration''. |