neděle 20. října 2019

Simple TLS certificates in WildFly 18

It's just 2 weeks when WildFly 18 was released. It includes nice improvements in TLS certificates handling through ACME protocol (Automatic Certificate Management Environment), it greatly simplifies obtaining valid HTTPS certificates.

There was already a support for the Let's Encrypt CA in WildFly 14 as Farah Juma described in her blog post last year.

New WildFly version allows using other CA-s with ACME protocol support.
It also adds new switch --lets-encrypt to interactive mode of security enable-ssl-http-server JBoss CLI commands. Let's try it.

Before we jump on WildFly configuration, let's just mention the HTTPs can be used even in the default configuration and a self-signed certificate is generated on the fly. Nevertheless, it's not secure and you should not use it for any other purpose than testing.

Use Let's Encrypt signed certificate for HTTPs application interface

Start WildFly on a machine with the public IP address. Run it on the default HTTP(80) and HTTPs(443) ports.

# run the following command as a root, because it's using privileged port numbers
bin/ -b \
  -Djboss.http.port=80 -Djboss.https.port=443
Connect JBoss CLI to the running WildFly instance:

bin/ --controller= --connect

and then run interactive Let's Encrypt configuration:

security enable-ssl-http-server --interactive --lets-encrypt

If you just confirm the defaults, agree to the Let's Encrypt terms of use and fill domain name(s), then the output can look like:
[standalone@ /] security enable-ssl-http-server --interactive --lets-encrypt
Please provide required pieces of information to enable SSL:

Let's Encrypt account key-store:
File name (default accounts.keystore.jks): 
Password (blank generated): 

Let's Encrypt certificate authority account:
Account name (default CertAuthorityAccount): 
Contact email(s) [,]: 
Password (blank generated): 
Alias (blank generated): 
Certificate authority URL (default 

Let's Encrypt TOS (
Do you agree to Let's Encrypt terms of service? y/n:y

Certificate info:
Key-store file name (default default-server.keystore): 
Password (blank generated): 
Your domain name(s) (must be accessible by the Let's Encrypt server at 80 & 443 ports) [,]:
Alias (blank generated): 
Enable SSL Mutual Authentication y/n (blank n):

Let's Encrypt options:
account key store name: account-key-store-b31e7f3d-8d16-46af-914e-91c3084a99d3
password: rRp8j1lw
account keystore file accounts.keystore.jks will be generated in server configuration directory.
Let's Encrypt certificate authority account name: CertAuthorityAccount
contact urls: []
password: crmYAvbS
alias: account-key-store-alias-b31e7f3d-8d16-46af-914e-91c3084a99d3
certificate authority URL:
You provided agreement to Let's Encrypt terms of service.

SSL options:
key store file: default-server.keystore
domain name: []
password: Gl2T6lVM
validity: 90
alias: alias-b31e7f3d-8d16-46af-914e-91c3084a99d3
Certificate will be obtained from Let's Encrypt server and will be valid for 90 days.
Server keystore file will be generated in server configuration directory.

Do you confirm y/n :y
Server reloaded.
SSL enabled for default-server
ssl-context is ssl-context-b31e7f3d-8d16-46af-914e-91c3084a99d3
key-manager is key-manager-b31e7f3d-8d16-46af-914e-91c3084a99d3
key-store   is key-store-b31e7f3d-8d16-46af-914e-91c3084a99d3

Let's verify the HTTPs access in the browser:
Everything works now!

Use HTTPs for management interface

If you already have the certificate for the application interface, you can simply reuse it for the management by setting the existing keystore name (generated in my case).

security enable-ssl-management --key-store-name=key-store-b31e7f3d-8d16-46af-914e-91c3084a99d3

In case you didn't enable the https for application interface and you want to just a valid certificate for the management interface, then use again the interactive way:

security enable-ssl-management --interactive --lets-encrypt

Simple, isn't it? :)

Žádné komentáře: