How to enable HTTPS in a Spring Boot Java application

Setting up HTTPS for Spring Boot is very easy, all you need to do is:

  1. Getting an SSL certificate;
  2. Configuring SSL in Spring Boot.

We can generate an SSL certificate ourselves (self-signed certificate). Its use is intended just for development and testing purposes. In production, you should use a certificate issued by a trusted Certificate Authority (CA). Whether you’re going to generate a self-signed certificate or you have already got one by a CA, I’ll show you how to enable HTTPS in a Spring Boot application.

how to enable HTTPS in Spring Boot - Thomas Vitale

In this tutorial I’ll explain how to:

  1. Get an SSL certificate
    • Generate a self-signed SSL certificate
    • Use an existing SSL certificate
  2. Enable HTTPS in Spring Boot
  3. Redirect HTTP requests to HTTPS
  4. Distribute the SSL certificate to clients.

If you don’t already have a certificate, follow the step 1a. If you have already got an SSL certificate, you can follow the step 1b.

Throughout this tutorial I’ll use the following technologies and tools:

  • Java JDK 8 (1.8.0_152)
  • Spring Boot 1.5.8.RELEASE
  • keytool
  • Spring Security 4.2.3.RELEASE (not required)

Keytool is a certificate management utility provided together with the JDK, so if you have the JDK installed, you should already have keytool available. To check it, try running the command keytool --helpfrom your Terminal prompt. Note that if you are on Windows, you might need to launch it from the \bin folder. For more information about this utility, you can read the official documentation.

1a. Generate a self-signed SSL certificate

First of all, you need to generate a pair of cryptographic keys, used them to produce an SSL certificate and store it in a keystore. In the keytool documentation, a keystore is defined as a database of “cryptographic keys, X.509 certificate chains, and trusted certificates”. To enable HTTPS, we’ll provide a Spring Boot application with this keystore containing the SSL certificate.

The two most common formats used for keystores are JKS, a proprietary format specific for Java, and PKCS12, an industry standard format. JKS used to be the default choice, but now Oracle recommends to adopt the PKCS12 format. I’ll show you how to use both.

Open your Terminal prompt and write the following command to create a JKS keystore:

keytool -genkeypair -alias tomcat -keyalg RSA -keysize 2048 -keystore keystore.jks -validity 3650

If you want to create a PKCS12 keystore, and you should, the command is the following:

keytool -genkeypair -alias tomcat -keyalg RSA -keysize 2048 -storetype PKCS12 -keystore keystore.p12 -validity 3650

You then will be asked to enter a password for the keystore. It must have at least 6 characters.

Enter keystore password:   
Re-enter new password:

Finally, you will be asked to input some information, but you are free to skip all of it (just press Return to skip an option). In the place of the first and last name, you may want to insert the base name of your host (in my case it is localhost).

What is your first and last name?
  [Unknown]: localhost
What is the name of your organizational unit?
What is the name of your organization?
What is the name of your City or Locality?
What is the name of your State or Province?
What is the two-letter country code for this unit?
Is CN=localhost, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
  [no]:  yes

Enter key password for <tomcat>
  (RETURN if same as keystore password):

At the end of this operation, we’ll get a keystore containing a brand new SSL certificate. To check the content of the keystore, we can use keytool again:

keytool -list -v -keystore keystore.jks

To test the content of a keystore following the PKCS12 format, you can use the following command:

keytool -list -v -storetype pkcs12 -keystore keystore.p12

If you have already created a JKS keystore and you want to migrate to PKCS12, keytool has a convenient command for that:

keytool -importkeystore -srckeystore keystore.jks -destkeystore keystore.p12 -deststoretype pkcs12

1b. Use an existing SSL certificate

If you have already got an SSL certificate, you can import it into a keystore and use it to enable HTTPS in a Spring Boot application.

Using the following command, you’ll create a new keystore containing your certificate.

keytool -import -alias tomcat -file myCertificate.crt -keystore keystore.p12 -storepass password

To get more information about the keystore and its format, please refer to the previous section.

2. Enable HTTPS in Spring Boot

Whether your keystore contains a self-signed certificate or one issued by a trusted Certificate Authority, we can now set up Spring Boot to accept requests over HTTPS instead of HTTP by using that certificate.

The first thing to do is placing the keystore file inside the Spring Boot project. You may want to put it in the resources folder or the root folder.

All you need to do is open up your file (if you have an application.yaml file, it works in the same) and define the following properties:

# Define a custom port instead of the default 8080
server.port = 8443

# Tell Spring Security (if used) to require requests over HTTPS

# The format used for the keystore 
# The path to the keystore containing the certificate
# The password used to generate the certificate
# The alias mapped to the certificate

You can specify a custom port using the server.port property (by default it is 8080). If your project is using Spring Security, you should set the security.require-ssl property to true to automatically block any requests coming from HTTP, without explicitly touching your Spring Security configuration class.

The server.ssl.key-store-type property defines the format used for the keystore (either JKS or PKCS12) while the server.ssl.key-store property contains the path to the keystore file (either keystore.jks or keystore.p12). In this case, we want Spring Boot to look for it in the classpath.

For more information about how to configure SSL in Spring Boot, you can have a look at the Reference Guide. If you want to find out which properties you can use to set SSL, you can refer to the definition.

Congratulations! You have successfully enabled HTTPS in your Spring Boot application! Give it a try: run the application, open your browser and check if everything works as it should.

3. Redirect HTTP requests to HTTPS

Now that we have enabled HTTPS in our Spring Boot application, we may want to redirect all traffic to HTTPS.

Spring allows defining just one network connector in the (or application.yaml) file. Since we have used it for HTTPS, we have to set the HTTP connector programmatically.

All we have to do is adding a new bean in a @Configuration class as shown in the following code.

public class ConnectorConfig {

  public EmbeddedServletContainerFactory servletContainer() {
    TomcatEmbeddedServletContainerFactory tomcat = new TomcatEmbeddedServletContainerFactory() {
      protected void postProcessContext(Context context) {
        SecurityConstraint securityConstraint = new SecurityConstraint();
        SecurityCollection collection = new SecurityCollection();

    return tomcat;

  private Connector getHttpConnector() {
    Connector connector = new Connector("org.apache.coyote.http11.Http11NioProtocol");

    return connector;


4. Distribute the SSL certificate to clients

If you’re using a self-signed SSL certificate, your browser won’t trust your application and will warn the user that it’s not secure. And that’ll be the same no matter the client.

It’s possible to make a client trust your application by providing it with your certificate. Since our certificate is stored inside the keystore, we need to extract it. Again, keytool supports us very well:

keytool -export -keystore keystore.jks -alias tomcat -file myCertificate.crt

To execute this command, you will be asked for the keystore password that you set at the beginning of this tutorial.

Now you can import your certificate into your client. In the next step, I’ll explain how to import the certificate into the JRE in case you need it to trust your application.

On the other hand, if you are using a keystore in PKCS12 format, you should be able to use it directly without extracting the certificate. I suggest you check the official guide on how to import a PKCS12 file into your browser. If you’re on macOS, you can directly import your certificate into the Keychain Access (which browsers like Safari, Chrome and Opera rely on to manage certificates).

If your application is deployed on your localhost, you may need to do a further step from your browser: enabling insecure connections with localhost. In Chrome, you do that by writing the following URL in the search bar: chrome://flags/#allow-insecure-localhost and activating the relative option.

Import the certificate inside the JRE keystore

To make the JRE trust your certificate, you need to import it inside cacerts: the JRE keystore in charge of holding certificates.

To do that, you’ll need to know the path to your JDK home. A quick way to find it, if you are using Eclipse or STS as your IDE, is by going to Preferences > Java > Installed JREs. Here you can read information about your JDK location. If you are using IntelliJ IDEA, you can access this information by going to Project Structure > SDKs and look at the value of the JDK home path field. On macOS it could be something like /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home. In the following, we’ll refer to this location by using the placeholder $JDK_HOME.

From your Terminal prompt insert the following command (you might need to run it with administrator privileges by prefixing it with sudo):

keytool -importcert -file myCertificate.crt -alias tomcat -keystore $JDK_HOME/jre/lib/security/cacerts

You’ll be asked to input the JRE keystore password. If you have never changed it, it should be the default one: changeit or changeme, depending on the operating system. Finally, you’ll be asked if you want to trust this certificate: say yes.

If everything went right, you’d see the message Certificate was added to keystore.


In this tutorial, we have seen how to generate a self-signed SSL certificate, how to import an existing certificate into a keystore, how to use it to enable HTTPS inside a Spring Boot application, how to redirect HTTP to HTTPS and how to extract and distribute the certificate to clients.

If you want to protect the access to some resources of your application, consider using Keycloak for the authentication and authorisation of the users visiting your Spring Boot application.

9 Replies to “How to enable HTTPS in a Spring Boot Java application”

    1. Hi, could you please give me some more information to better understand what could be the problem? Thanks!

      I’ve just updated my tutorial, I hope it’ll be clearer now.

  1. How would I do this, when I want to use an issued certifcate file like .cer from a ssl provider?
    Do i need to bundle the entire ssl chain into a jks file on the server?

    1. Hi Iskandar, thanks for asking, I took the chance to update my tutorial to include explanations about what to do with certificates issued by some CA.

      Shortly, the process is still the same, you just need to import your certificate inside a keystore. Please let me know if it is clear the new part of my tutorial dealing with this case, thank you.

    1. Hi Rahul, thanks for your comment. I’ve just updated this tutorial to make it clearer, provide more and better information and correct a couple of confusing points.

      The part related to cacerts is not needed to enable https on Spring Boot, it’s just used to make the JRE trust your self-signed certificate. It is an optional step, you can skip it.

      Spring Boot just uses the keystore file to get the SSL certificate and enable https. And you can place this file inside the Spring Boot project (for example in the root folder or under resources).

      Let me know if you have more doubts about it.

      1. After all steps, on running spring app, browser shows https secure warning.
        Is it handled by certificate itself?

  2. Hi,
    I have done it properly but when I launch web app, browser shows the warning ‘This is not secure’. I have to enable https in browser. Is it possible in certificate?

    1. Hi Akshit,

      if your app is using a self-signed certificate, a good browser should show the warning since it can’t verify the validity and authentication of the certificate. To make a browser recognise a self-signed certificate on your local machine, you can import your certificate (as explained in point 4) into your browser or, better, directly in your operating system.

      These are some official guides to do that:
      Google Chrome
      Mozilla Firefox
      Keychain Access (for macOS)
      Certificate Store (for Windows).

      After doing that, restart your browser/machine.

      Depending on your browser settings and if your application is running on the localhost, you may see the warning anyway. If it’s your case, you could try adding an exception in your browser for your application.

      A good resource to get started with SSL certificates is this white paper published by Symantec.

      Let me know if something is not clear or you have more questions!

Leave a Reply

Your email address will not be published. Required fields are marked *