Skip to main content

Configuring HTTPS in Spring Boot: A Step-by-Step Guide

Configuring HTTPS in Spring Boot: A Step-by-Step Guide

Configuring HTTPS in Spring Boot: A Step-by-Step Guide

Introduction

In today's digital landscape, ensuring the security of web applications is paramount. One of the fundamental ways to achieve this is by enabling HTTPS. In this guide, we'll walk you through the process of configuring HTTPS in a Spring Boot application, step by step.

Prerequisites

Before we dive in, make sure you have a basic understanding of Spring Boot and Java. You should also have a Spring Boot application set up and ready to go.

Step 1: Generate or Obtain an SSL/TLS Certificate

An SSL/TLS certificate is essential for establishing secure communication. Let's start by generating a self-signed certificate using keytool, which is included with the Java JDK:

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

Step 2: Place the Certificate in the Resources Folder

Store the generated keystore.p12 file in the src/main/resources folder of your Spring Boot application.

Step 3: Configure application.properties or application.yml

Update your Spring Boot configuration file (application.properties or application.yml) with the following properties:

For application.properties:

server.port=8443
server.ssl.key-store=classpath:keystore.p12
server.ssl.key-store-password=your-keystore-password
server.ssl.key-store-type=PKCS12
server.ssl.key-alias=mycert

For application.yml:

server:
  port: 8443
  ssl:
    key-store: classpath:keystore.p12
    key-store-password: your-keystore-password
    key-store-type: PKCS12
    key-alias: mycert

Step 4: Update Security Configuration (if applicable)

If your application has security configurations, ensure they are adjusted to support secure endpoints. For example, in a Spring Security configuration, you might need to modify access rules to require HTTPS.

Step 5: Run the Application

With the configuration in place, run your Spring Boot application. It will now be accessible over HTTPS at https://localhost:8443.

Additional Considerations for Production

While self-signed certificates are suitable for testing, production environments require trusted certificates from a Certificate Authority (CA). Additionally, consider using a reverse proxy server like Apache or Nginx for added security and performance.

Conclusion

By following these steps, you've successfully configured HTTPS in your Spring Boot application. Secure communication is crucial for protecting sensitive data and ensuring the trust of your users.

Additional Resources

Comments

Popular posts from this blog

Offline AI Coding in VSCode: Continue + Ollama Complete Setup Guide

Want GitHub Copilot-level code assistance — but fully offline, air-gapped, and private? This guide walks you through setting up Continue (a VSCode extension) with Ollama (a local model runner) so you get chat, autocomplete, and inline editing powered entirely by models running on your own machine. No internet required at runtime. Table of Contents What Are Continue and Ollama? Prerequisites & Hardware Requirements Choosing the Right Models Step 1 — Installing Ollama & Pulling Models Step 2 — Installing Continue in VSCode (Offline) Step 3 — Configuring config.yaml Step 4 — Disabling Telemetry Step 5 — Usage & Shortcuts Troubleshooting What Are Continue and Ollama? Continue is an open-source VSCode (and JetBrains) extension that adds AI-powered coding features directly into your editor — think chat, inline edits, and tab autocomplete. By default it can connect to Claude, GPT-4, or any API. But it also supports local providers , which is exactly what we want here. Ollama i...

Local LLM on Ubuntu (CPU-Only): Ollama + Qwen Coder + Open WebUI + RAG Setup

Local LLM on Ubuntu (CPU-Only): Ollama + Qwen Coder + Open WebUI + RAG Run a private, high-performance internal AI coding assistant on your own hardware—no GPU required. Feb 13, 2026 Qwen 2.5 Coder RAG Enabled Enterprise Ready Keeping your code and documents on your own infrastructure is the gold standard for enterprise security. By combining Ollama , Qwen Coder , and Open WebUI , we can build a production-grade AI assistant that respects your privacy. Environment: CPU-only Ubuntu server (e.g., i9/Threadripper) with 64GB+ RAM for smooth 14B model inference. 1. System Preparation First, update your local environment and install necessary dependencies: sudo apt update && sudo apt upgrade -y sudo apt install -y curl git ca-certificates lscpu 2. Ollama & Model Tuning Install Ollama and optimize the configuration for CPU-only inference by setting the thread count: ...

Defining tomcat and mysql server Amazon EC2 instance

-- Create new amazon ec2 instance http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html -- Give permisson to pem file chmod 400 mycertificate.pem -- Connect to EC2 instance ssh -i mycertificate.pem ubuntu@ec2-51-51-51-51.eu-west-1.compute.amazonaws.com -- Installation Oracle Java 1.8 $ wget --no-check-certificate --no-cookies --header "Cookie: oraclelicense=accept-securebackup-cookie" http://download.oracle.com/otn-pub/java/jdk/8u92-b14/jdk-8u92-linux-x64.tar.gz $ tar -xzvf jdk-8u92-linux-x64.tar.gz $ sudo mkdir -p /usr/java/ $ sudo mv jdk1.8.0_92/ /usr/java/ $ sudo vim  /etc/profile         JAVA_HOME=/usr/java/jdk1.8.0_92         PATH=$PATH:$HOME/bin:$JAVA_HOME/bin         JRE_HOME=/usr/java/jdk1.8.0_92/jre         PATH=$PATH:$HOME/bin:$JRE_HOME/bin         export JAVA_HOME...