Introduction

Various pages of the CoreOne Authentication Service can be changed or adapted by overriding the appropriate file. This document aims to give you an overview of those files.

Branding

Most of the look and feel of the CoreOne Authentication Service can be branded according to your CI/CD. This is mostly done by overriding the default files in the following directory:

In there you will find a file, containing all the resources that were requested so far:

The content of that file looks similar to this:

As you can see, there is a file where you can place your specific overall changes (Line 1). Those files are also localized, so if you want to do culture specific changes, you can use those files (Line 2). There are also page specific changes that you can make (Line 3) or file specific changes (Line 5).

General vs Client specific changes

Generally there are also two root folders. One called general, where the general changes can be made. Those changes will apply to all applications and clients. But you might wanna change the look and feel only for a given client. You can achieve this by overriding the files in the clientspecific folder. Just select the folder of your client there and follow the same logic as you would for general changes.

For a quick example of such changes you can read the How-to change the logo of the CoreOne Authentication Service How-To change the logo of the CoreOne Authentication Service.

Default layout

The layout of the CoreOne Authentication Service looks like displayed below. This should give you a broad idea on where to start with your design changes.

Translation

If you want to change any of the texts, you can do so by changing the appropriate translation files located in the following directory:

All the default translations are store in the following file. So just search for the text to find the appropriate key:

If you then want to change it, just add the appropriate value to the appropriate override file. So for example if you want to change the default text of the “Login” button in german, add the following entry to the following file:

Error Messages

Whenever something unexpected is happening, a general error page is rendered with some information about the error. For example if the user has an SMS OTP configured, but the SMS gateway is currently unavailable, an appropriate message is rendered. On this generic error page, there is also a contacts section that you can fill with the appropriate contact details. In order to display this contact details, set the appropriate translation key:

Note that this will be rendered as HTML Raw. So you can place HTML content into the translation.

Welcome Page

If you would like to add customer specific content to the CoreOne Authentication Service Welcome page, you can do so by specifying the appropriate content here: