Thymeleaf + Spring Security integration basics

Have you switched to Thymeleaf but your login and error pages are still using JSP? In this article we will see how to configure your Spring application to use Thymeleaf for login and error pages.

All the code seen here comes from a working application. You can view or download the source code from its GitHub repo.


We asume you are familiar with Thymeleaf and Spring Security, and you have a working application using these technologies. If you don’t know Spring Security, you could be interested on reading the Spring Security Documentation.

Login pages

With Spring Security you could specify any URL to act as a login page, just like:

protected void configure(final HttpSecurity http) throws Exception {

Now we have to match these pages inside a Spring Controller:

public class MainController {


  // Login form
  public String login() {
    return "login.html";

  // Login form with error
  public String loginError(Model model) {
    model.addAttribute("loginError", true);
    return "login.html";


Note that we are using the same template login.html for both pages, but when there is an error, we set a boolean attribute into the model.

Our login.html template is as follows:

<!DOCTYPE html>
<html xmlns:th="">
    <title>Login page</title>
    <h1>Login page</h1>
    <p th:if="${loginError}" class="error">Wrong user or password</p>
    <form th:action="@{/login.html}" method="post">
      <label for="username">Username</label>:
      <input type="text" id="username" name="username" autofocus="autofocus" /> <br />
      <label for="password">Password</label>:
      <input type="password" id="password" name="password" /> <br />
      <input type="submit" value="Log in" />

Error page

We can also configure an error page based on Thymeleaf . In this case Spring Security is not involved at all, we should simply add an ExceptionHandler to our Spring configuration like:

public class ErrorController {

    private static Logger logger = LoggerFactory.getLogger(ErrorController.class);

    public String exception(final Throwable throwable, final Model model) {
        logger.error("Exception during execution of SpringSecurity application", throwable);
        String errorMessage = (throwable != null ? throwable.getMessage() : "Unknown error");
        model.addAttribute("errorMessage", errorMessage);
        return "error";


The error.html template could be like:

<!DOCTYPE html>
<html xmlns:th="">
        <title>Error page</title>
        <meta charset="utf-8" />
        <link rel="stylesheet" href="css/main.css" th:href="@{/css/main.css}" />
    <body th:with="httpStatus=${T(org.springframework.http.HttpStatus).valueOf(#response.status)}">
        <h1 th:text="|${httpStatus} - ${httpStatus.reasonPhrase}|">404</h1>
        <p th:utext="${errorMessage}">Error java.lang.NullPointerException</p>
        <a href="index.html" th:href="@{/index.html}">Back to Home Page</a>

Note how we are using Spring’s HttpStatus enum in order to obtain detailed information about the response status that has been set (which in this case will always be 500, but this allows us to use this error.html in other error reporting scenarios).

Spring Security Dialect

The Spring Security 3 integration module is a Thymeleaf dialect equivalent to Spring security taglib.

We use this dialect in the example in order to print the logged user credentials and to show different content to different roles.

The sec:authorize attribute renders its content when the attribute expression is evaluated to true:

<div sec:authorize="isAuthenticated()">
  This content is only shown to authenticated users.
<div sec:authorize="hasRole('ROLE_ADMIN')">
  This content is only shown to administrators.
<div sec:authorize="hasRole('ROLE_USER')">
  This content is only shown to users.

The sec:authentication attribute is used to print logged user name and roles:

Logged user: <span sec:authentication="name">Bob</span>
Roles: <span sec:authentication="principal.authorities">[ROLE_USER, ROLE_ADMIN]</span>