Themes - Home - FusionAuth

1. Overview

FusionAuth themes allow you to customize the OAuth2 / OpenID Connect login pages and other user workflows such as forgot password. In FusionAuth you may create one to many themes and assign a theme per tenant so that you can customize the user experience for different users.

In this guide you will find a video demonstration, a list of each template available to you and some example code.

Example Video
Create a Theme
Example Code
Template Variables
Handling Failures

2. Example Video

To demonstrate what is possible with the FusionAuth feature we have created a video that illustrates how to make FusionAuth look like StackOverflow.

3. Create a Theme

FusionAuth provides the ability to create and manage themes in the UI as well as a Themes API if you prefer to manage themes programatically. Any user of the FusionAuth role of admin or theme_manager may view, edit, update, and delete Themes.

All of the FusionAuth login templates are written in FreeMarker. FreeMarker provides a very rich template language that will allow you to customize the pages and helpers to suit your needs. You can also define new macros and function to assist you further.

Below is an example screenshot of the Add Theme panel with each template described below.

Table 1. Form Fields
Id Optional	An optional UUID. When this value is omitted a unique Id will be generated automatically.
Name Required	A unique name to identity the theme. This name is for display purposes only and it can be modified later if desired.

Table 2. Templates
Stylesheet (CSS) Optional	This CSS stylesheet may be used to style the themed pages. This CSS will be included in the `head` tag in the Helpers `head` macro. You may also choose to include other remote stylesheets by using the `<style>` tag within the `head` macro. `<style> ${theme.stylesheet()} </style>`
Messages Optional	This section allows you to add additional localized messages to your theme. When creating an additional locale it is not required that all messages are defined for each language. If a message key is not defined for the specified locale, the value from the default bundles will be used. If you intend to localize your login templates, you may find our community contributed and maintained messages in our GitHub repository. https://github.com/FusionAuth/fusionauth-localization
Helpers Required	This template contains all of the main helper macros to define the `head`, `body` and `footer`. To begin theming FusionAuth you’ll want to start with this template as it will affect all other templates. See Helpers section below for additional information.
Email verification complete Required	This page is used after a user has verified their email address by clicking the URL in the email. After FusionAuth has updated their user object to indicate that their email was verified, the browser is redirected to this page. /email/complete
Email verification re-send Required	This page is used after a user has asked for the verification email to be resent. This can happen if the URL in the email expired and the user clicked it. In this case, the user can provide their email address again and FusionAuth will resend the email. After the user submits their email and FusionAuth re-sends a verification email to them, the browser is redirected to this page. /email/send
Email verification Required	This page is rendered when a user clicks the URL from the verification email and the `verificationId` has expired. FusionAuth expires `verificationId` after a period of time (which is configurable). If the user has a URL from the verification email that has expired, this page will be rendered and the error will be displayed to the user. /email/verify
OAuth authorize Required	This is the main login page for FusionAuth and is used for all interactive OAuth2 and OpenID Connect workflows. /oauth2/authorize
OAuth child registration not allowed Required	This page contains a form where a child must provide their parent’s email address to ask their parent to create an account for them in a Consent workflow. /oauth2/child-registration-not-allowed
OAuth child registration not allowed complete Required	This page is rendered is rendered after a child provides their parent’s email address for parental consent in a Consent workflow. /oauth2/child-registration-not-allowed-complete
OAuth complete registration Required	This page contains a form that is used for users that have accounts but might be missing required fields. /oauth2/complete-registration
OAuth device Required	This page contains a form for accepting an end user’s short code for the interactive portion of the OAuth Device Authorization Grant workflow. /oauth2/device
OAuth error Required	This page is used if the user starts or is in the middle of the OAuth workflow and any type of error occurs. This could be caused by the user messing with the URL or internally some type of information wasn’t passed between the OAuth endpoints correctly. For example, if you are federating login to an external IdP and that IdP does not properly echo the `state` parameter, FusionAuth’s OAuth workflow will break and this page will be displayed. /oauth2/error
OAuth logout Required	This page is used if the user initiates a logout. This page causes the user to be logged out of all associated applications via a front-channel mechanism before being redirected. /oauth2/logout
OAuth passwordless Required	This page is rendered when the user starts the passwordless login workflow. The page renders the form where the user types in their email address. /oauth2/passwordless
OAuth register Required	This page is used to register the user for the application. /oauth2/register
OAuth two-factor Required	This page is used if the user has two-factor authentication enabled and they need to type in their code again. FusionAuth will properly handle the SMS or authenticator app processing on the back end. This page contains the form that the user will put their code into. /oauth2/two-factor
OAuth Change password form Required	This page is used if the user is required to change their password or if they have requested a password reset. This page contains the form that allows the user to provide a new password. /password/change
OAuth password password complete Required	This page is used after the user has successfully updated their password (or reset it). This page should instruct the user that their password was updated and that they need to login again. /password/complete
Forgot password Required	This page is used when a user starts the forgot password workflow. This page renders the form where the user types in their email address. /password/forgot
Forgot password sent Required	This page is used when a user has submitted the forgot password form with their email. FusionAuth does not indicate back to the user if their email address was valid in order to prevent malicious activity that could reveal valid email addresses. Therefore, this page should indicate to the user that if their email was valid, they will receive an email shortly with a link to reset their password. /password/sent
Verify registration complete Required	This page is used after a user has verified their email address for a specific application (i.e. a user registration) by clicking the URL in the email. After FusionAuth has updated their registration object to indicate that their email was verified, the browser is redirected to this page. /registration/complete
Verify registration send Required	This page is used after a user has asked for the application specific verification email to be resent. This can happen if the URL in the email expired and the user clicked it. In this case, the user can provide their email address again and FusionAuth will resend the email. After the user submits their email and FusionAuth re-sends a verification email to them, the browser is redirected to this page. /registration/send
Verify registration Required	This page is used when a user clicks the URL from the application specific verification email and the `verificationId` has expired. FusionAuth expires `verificationId` after a period of time (which is configurable). If the user has a URL from the verification email that has expired, this page will be rendered and the error will be displayed to the user. /registration/verify

4. Helpers

In addition to the pages listed above, FusionAuth has a template that contains a number of macros used in all of the page templates. This template is located at ../_helpers.ftl and it contains a number of FreeMarker macros. The rest of the pages use these macros to generate various pieces of the HTML. The macros contained in _helpers.ftl are:

4.1. Section Helpers

html
- Renders the <html> element
head
- Renders the <head> element and everything inside it including the <title>, CSS, Java Script, and meta information
body
- Renders the <body> element
header
- Renders any type of header for each page. This could be a navigation bar, side bar, or page details
main
- Renders the main content body of each page. If all of your pages will have similar HTML elements like a container, this is the place to put them.
footer
- Renders the footer content of each page. This might contain links, nav, privacy policies, etc.

Here is an example of what one of these helpers looks like:

HTML helper

[#macro html]
<!DOCTYPE html>
<html>
  [#nested/]
</html>
[/#macro]

The key to these macros is the [#nested/] element. This is the location that FreeMarker will insert any nested content when you use the macro. Here is an example of using this macro:

Example usage of HTML macro

[@helpers.html]
<body>
Hello world!
</body>
[/@helpers.html]

Everything inside the macro will be place where the [#nested/] element is. Therefore, the result of our example would be this HTML:

Example result

<!DOCTYPE html>
<html>
<body>
Hello world!
</body>
</html>

All of the page templates use these macros, which makes it much easier to style all of the pages at one time. You simply edit the macros and your changes will take effect on all of the pages listed above.

In addition to the section helpers, the _helpers.ftl template also contains a few additional macros that can be used to setup social and alternative logins. Currently, FusionAuth supports these social login providers:

Facebook
Google
Twitter
Generic OpenID Connect

Once you have configured your alternative logins (called identity providers in the interface and API), they will appear on the FusionAuth stock login form. This is because our stock login form includes this code:

Social login code

[@helpers.head]
  [@helpers.alternativeLoginsScript clientId=client_id identityProviders=identityProviders/]
  ...
[/@helpers.head]

[@helpers.body]
  ...

  [@helpers.alternativeLogins clientId=client_id identityProviders=identityProviders/]
[/@helpers.body]

The first macro (alternativeLoginScripts) includes the JavaScript libraries that FusionAuth uses to hook up the identity providers. Unless you want to write your own JavaScript or use a third-party library, you will need this JavaScript in the <head> tag in order for FusionAuth to leverage external login providers.

The second macro (alternativeLogins) produces the login buttons for each of the configured identity providers. These buttons are all hooked up to the JavaScript included in the <head> of the page in order to make it all work nicely.

You might want to use your own buttons for social logins. This is possible with FusionAuth, but you will need to do a couple of things to make it all work.

First, you need to remove the [@helpers.alternativeLogins] macro call.

Second, you need to use a specific id or class on your HTML element for the button. Here are the id s or class es for each identity provider:

id="google-login-button" is used for Google
id="facebook-login-button" is used for Facebook
id="twitter-login-button" is used for Twitter
class="openid login-button" is used for Generic OpenID Connect

And finally, you need to ensure that Prime.js is included on your page. This library ships with FusionAuth and you just need to ensure it is included like this:

Prime.js include

<script src="/js/prime-min.js"></script>

4.3. Alert and Error Helpers

The _helpers.ftl template also provides a couple of macros that can be used to output errors and alerts that might occur. The best bet is to include these macros in your main macro. Here are the macros and their purpose:

printErrorAlerts
- This outputs any error alerts. These are normally displayed at the top of the page and you might want to make them able to be dismiss (i.e. removed from the page).
printInfoAlerts
- This outputs any informational alerts. These are the same as the errors, but might have different CSS.
alert
- This macro is used by the printErrorAlerts and printInfoAlerts but you can also use it directly to display an error or info message anywhere on the page.

4.4. Form Helpers

The _helpers.ftl template also provides a couple of macros that help render form elements and output form errors. Here are the macros you can use:

hidden
- This outputs a hidden input element. Many pieces of the OAuth workflow and the other pages in FusionAuth use hidden form fields to store data. This macro uses the eval feature of FreeMarker in order to pull in data that was in the request. You shouldn’t edit this macro unless you know what you are doing.
input
- This outputs an input element plus a label and any errors that might have occurred on the form field. You can use this for text, passwords, and other input elements. FusionAuth also leverages addons which are icons next to the input field that provide visual cues to the user. This macro allows you to leverage addons as well. Similar to the hidden element, you should not edit this unless you know what you are doing.
errors
- This macro is used by the input macro to render errors on the field. You can use this if you write your own input macros. Otherwise, you likely won’t use this.
button
- This macro renders a button that can be used to submit a form. The FusionAuth version of this macro includes an icon and the button text.

5. Example Code

5.1. Example of Customizing the Authorize Page

Now that you have a good overview of all the templates, macros and helpers, here is an example of customizing the Authorize page.

Let’s assume you want to change the header and footer across all of the pages including the Authorize page. This is accomplished by editing the helpers.header and helpers.footer macros. For the header, let’s assume you want to add a Sign Up and Login link. For the footer, let’s assume you want to add a link to your privacy policy. Here are the macros that include these new links:

Custom header helper

[#macro header]
  <header class="my-custom-header">
    <nav>
      <ul>
        <li class="login"><a target="_blank" href="https://my-application.com/login">Login</li>
        <li class="sign-up"><a target="_blank" href="https://my-application.com/sign-up">Sign Up</li>
      </ul>
    </nav>
  </header>

  [#nested/]
[/#macro]

Custom footer helper

[#macro footer]
  <footer class="my-custom-footer">
    <nav>
      <ul>
        <li class="privacy-policy"><a target="_blank" href="https://my-application.com/privacy-policy">Privacy Policy</li>
      </ul>
    </nav>
  </footer>

  [#nested/]
[/#macro]

Once you make these changes, they will take effect on all of the pages listed above.

6. Template Variables

Each template has different variables that are available to it. These variables can be used in the template to help with rendering the HTML. There are also a couple of common variables that are available in all of the pages. The common variables and the page specific variables are all listed below:

6.1. Common Variables

Table 3. Variables
errorMessages [List<String>]	A list of error messages that were generated during the processing of the request.
fieldMessages [Map<String, List<String>>]	A map of field messages (usually errors) that were generated during the processing of the request. The key into the map is the name of the form field and the value is a list that contains the errors for that form field.
locale [Locale]	The locale used to localize messages. You can find the JavaDoc for this object available here: https://docs.oracle.com/javase/8/docs/api/java/util/Locale.html
request [HttpServletRequest]	The HttpServletRequest object that is part of the Java Servlet specification. You can find the JavaDoc for this object available here: https://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServletRequest.html
tenant [Tenant]	The tenant that has been resolved for this template. This value has either been specified on the request by providing the `tenantId` request parameter or it has been resolved by other request parameters such as the `client_id`. See the Tenant API for details on this object.
tenantId [UUID]	The unique Tenant identifier, this is equivalent to `tenant.id`.

6.2. `/email/complete`

No page specific variables.

6.3. `/email/send`

Table 4. Variables
email [String]	The email address that was passed as a URL parameter. This is the email address that is requesting that the verification email be re-sent to.
emailSent [Boolean]	A boolean that indicates if the verification email was re-sent or not.

6.4. `/email/verify`

Table 5. Variables
verificationId [String]	The verification id that was included on as a URL parameter but was invalid. This page does a redirect if the verificationId is valid.

6.5. `/oauth2/authorize`

Table 6. Variables
client_id [String]	The OAuth v2.0 `client_id` parameter. This is synonymous with FusionAuth’s Application Id.
hasDomainBasedIdentityProviders [Boolean]	A boolean that indicates if there are domain-based identity providers configured. These identity providers use the user’s email address to determine if an external IdP should be used to log the user in.
identityProviders [Map<String, List<Object>>]	A map of the configured identity providers for the Application the user is logging into. The key into the map is the type of the identity provider (i.e. `Facebook` or `OpenIDConnect`). The value is a list of all of the configured identity providers for that type. NOTE: This map does not contain any "domain-based" identity providers since those are handled differently using just the Email input field to start and then possibly redirecting the browser to the external IdP login page.
loginId [String]	The value from the `loginId` form field. This is either the username or the email of the user attempting to log into FusionAuth.
nonce [String]	The OpenID Connect `nonce` request parameter.
redirect_uri [String]	The OAuth v2.0 `redirect_uri` parameter. This is the URI that FusionAuth will redirect the user to once they have successfully logged in.
response_type [String]	The OAuth v2.0 `response_type` parameter.
scope [String]	The OAuth v2.0 `scope` parameter.
showPasswordField [Boolean]	A boolean that controls whether or not the `password` field is shown if there are domain-based identity providers. If there are domain based identity providers and the user types in an email address that is not managed by the identity provider, FusionAuth will then re-render this template with this variable set to `true`. This will indicate that the password field should be shown so that the user can complete their login. If you need an example of this behavior, check out the login page at https://www.pivotaltracker.com/signin.
state [String]	The OAuth v2.0 `state` parameter.
timezone [String]	The timezone that the user is in. This is normally guessed by the timezone JavaScript library (or something similar) and then stored in a hidden input field on the login form.

6.6. `/oauth2/child-registration-not-allowed`

Table 7. Variables
parentEmail [String]	The parent’s email address provided in the input field of the form. .

6.7. `/oauth2/child-registration-not-allowed-complete`

No page specific variables.

6.8. `/oauth2/device`

Table 8. Variables
client_id [String]	The OAuth v2.0 `client_id` parameter. This is synonymous with FusionAuth’s Application Id.
activationComplete [Boolean]	Whether or not the Device Authorization Grant flow has been completed.
code [String]	A authorization code on the redirect returned from an interactive login.
interactive_user_code [String]	The user code provided by the user in the form.
userCodeLength [int]	The length of the interactive user code.

6.9. `/oauth2/error`

Table 9. Variables
oauthJSONError [String]	The OAuth error JSON that could be helpful for developers while debugging.

6.10. `/oauth2/logout`

Table 10. Variables
allLogoutURLs [Set<String>]	A set of URLs associated with all of the applications in the tenant to log out the user.
registeredLogoutURLs [Set<String>]	A set of URLs associated with all of the applications the user is registered for to log out the user.
redirectURL [String]	The URL to be redirected to after the front-channel logouts occur.

6.11. `/oauth2/passwordless`

Table 11. Variables
client_id [String]	The OAuth v2.0 `client_id` parameter. This is synonymous with FusionAuth’s Application Id.
redirect_uri [String]	The OAuth v2.0 `redirect_uri` parameter. This is the URI that FusionAuth will redirect the user to once they have successfully logged in.
response_type [String]	The OAuth v2.0 `response_type` parameter.
scope [String]	The OAuth v2.0 `scope` parameter.
state [String]	The OAuth v2.0 `state` parameter.
timezone [String]	The timezone that the user is in. This is normally guessed by the timezone JavaScript library (or something similar) and then stored in a hidden input field on the login form.

6.12. `/oauth2/register`

Table 12. Variables
collectBirthDate [Boolean]	Whether or not to collect a birth date for a Consent workflow.
hideBirthDate [Boolean]	Whether or not to render a hidden field for passing along the birthdate in the form.
parentEmailRequired [Boolean]	Whether or not a parent’s email address is required for a Consent Workflow.
passwordValidationRules [Object]	An object that contains the password validation rules. The object fields are defined below.
passwordValidationRules.maxLength [int]	The maximum length of a password.
passwordValidationRules.minLength [int]	The minimum length of a password.
passwordValidationRules.rememberPreviousPasswords.count [Object]	The number of previous passwords the user is not allowed to re-use.
passwordValidationRules.requireMixedCase [Boolean]	Whether or not the user must use upper and lower-cased letter.
passwordValidationRules.requireNonAlpha [Boolean]	Whether or not the user must use at least one non-alphabetic character in their password.
passwordValidationRules.requireNumber [Boolean]	Whether or not the user must use at least one numeric character in their password.

6.13. `/oauth2/two-factor`

Table 13. Variables
client_id [String]	The OAuth v2.0 `client_id` parameter. This is synonymous with FusionAuth’s Application Id.
code [String]	The value of the `code` form field on the page. This will be available only after the user has submitted the form.
device [String]	The device identifier that user is using to log in.
grant_type [String]	The OAuth v2.0 `grant_type` parameter.
pushEnabled [Boolean]	Whether or not FusionAuth has pushed (SMS) enabled for two-factor.
pushPreferred [Boolean]	Whether or not the user prefers push (SMS) for two-factor.
redirect_uri [String]	The OAuth v2.0 `redirect_uri` parameter. This is the URI that FusionAuth will redirect the user to once they have successfully logged in.
resendCode [Boolean]	Whether or not the user wants the code to be resent to their phone (valid for push two-factor).
response_type [String]	The OAuth v2.0 `response_type` parameter.
scope [String]	The OAuth v2.0 `scope` parameter.
trustComputer [Boolean]	The value of the "Trust this computer" form field. This will be available only after the user has submitted the form. Otherwise, it defaults to false.
state [String]	The OAuth v2.0 `state` parameter.
timezone [String]	The timezone that the user is in. This is normally guessed by the timezone JavaScript library (or something similar) and then stored in a hidden input field on the login form.
userCanReceivePush [Boolean]	Whether or not the user is capable of receiving push notifications for two-factor. This means that the user has a mobile phone number.

6.14. `/password/change`

Table 14. Variables
changePasswordId [String]	The id that was sent to the user (usually via email) that allows them to change their password. Normally, this id is included in the email template for the `forgot password` workflow and when the user clicks the link in the email, they are taken to this page with this parameter on the URL.
passwordValidationRules [Object]	An object that contains the password validation rules. The object fields are defined below.
passwordValidationRules.maxLength [int]	The maximum length of a password.
passwordValidationRules.minLength [int]	The minimum length of a password.
passwordValidationRules.rememberPreviousPasswords.count [Object]	The number of previous passwords the user is not allowed to re-use.
passwordValidationRules.requireMixedCase [Boolean]	Whether or not the user must use upper and lower-cased letter.
passwordValidationRules.requireNonAlpha [Boolean]	Whether or not the user must use at least one non-alphabetic character in their password.
passwordValidationRules.requireNumber [Boolean]	Whether or not the user must use at least one numeric character in their password.

6.15. `/password/complete`

No page specific variables.

6.16. `/password/forgot`

No page specific variables.

6.17. `/password/sent`

No page specific variables.

6.18. `/registration/complete`

No page specific variables.

6.19. `/registration/send`

Table 15. Variables
applicationId [UUID]	The id of the application that the user is verifying their email for and needs the email to be resent.
email [String]	The email address that was passed as a URL parameter. This is the email address that is requesting that the verification email be re-sent to.
emailSent [Boolean]	A boolean that indicates if the verification email was re-sent or not.

6.20. `/registration/verify`

Table 16. Variables
verificationId [String]	The verification id that was included on as a URL parameter but was invalid. This page does a redirect if the verificationId is valid.

7. Handling Failures

If you happen to get into a situation where you have edited a template and it is causing errors that are preventing you from logging in, you can override the use of the UI templates to render a login form that lets you log in. To do this, open your browser and access your FusionAuth admin UI. This will redirect you to the broken /oauth2/authorize page. Click in your browsers address bar and scroll to the end. Finally, add the String &bypassTheme=true to the end of the URL and hit the Enter key. This should render the default login page that ships with FusionAuth and allow you to log in and fix any errors you have.

1. Overview

2. Example Video

3. Create a Theme

4. Helpers

4.1. Section Helpers

4.2. Social (alternative) Login Helpers

4.3. Alert and Error Helpers

4.4. Form Helpers

5. Example Code

5.1. Example of Customizing the Authorize Page

6. Template Variables

6.1. Common Variables

6.2. /email/complete

6.3. /email/send

6.4. /email/verify

6.5. /oauth2/authorize

6.6. /oauth2/child-registration-not-allowed

6.7. /oauth2/child-registration-not-allowed-complete

6.8. /oauth2/device

6.9. /oauth2/error

6.10. /oauth2/logout

6.11. /oauth2/passwordless

6.12. /oauth2/register

6.13. /oauth2/two-factor

6.14. /password/change

6.15. /password/complete

6.16. /password/forgot

6.17. /password/sent

6.18. /registration/complete

6.19. /registration/send

6.20. /registration/verify

7. Handling Failures

6.2. `/email/complete`

6.3. `/email/send`

6.4. `/email/verify`

6.5. `/oauth2/authorize`

6.6. `/oauth2/child-registration-not-allowed`

6.7. `/oauth2/child-registration-not-allowed-complete`

6.8. `/oauth2/device`

6.9. `/oauth2/error`

6.10. `/oauth2/logout`

6.11. `/oauth2/passwordless`

6.12. `/oauth2/register`

6.13. `/oauth2/two-factor`

6.14. `/password/change`

6.15. `/password/complete`

6.16. `/password/forgot`

6.17. `/password/sent`

6.18. `/registration/complete`

6.19. `/registration/send`

6.20. `/registration/verify`