The following provides information on customizing different parts of the EJBCA user interface.

CA User Interface

You can customize the CA UI in a number of ways:

System Configuration>Basic Configurations>Title
- Edit the HTML page title of the CA UI (visible in the top of your web browser and in bookmarks)
System Configuration>Basic Configurations→Head Banner
- Can be changed to one of the pre-shipped versions: adminweb/banners/head_banner.jsp, adminweb/banners/head_banner_test.jsp, adminweb/banners/head_banner_acc.jsp, adminweb/banners/head_banner_warning.jsp
- On a pure software installation, you can create additional banners by creating a new file in modules/admin-gui/resources/banners, re-deploying EJBCA and selecting your custom banner.
System Configuration>Administrator Preferences>Theme
- You can select one of the pre-defined themes that are stored in modules/admin-gui/resources/themes. The selection here will be the default in My Preferences for new administrators, where administrators can select their own theme.

RA User Interface

The entire CSS of the RA Web can be customized and hot-deployed by uploading a custom CSS package on the CA Web (which in the case of a remote RA connected by Peers will be automatically downloaded and deployed). For more information, see Customizing the RA Appearance.

Public Web

Public Web is deprecated as of EJBCA 7.9 and will no longer be supported as of the next major version of EJBCA.

The Public Web pages are written in JSP and can be found under modules/publicweb-gui/resources/. You can modify the pages (directly or by using a separate tree), rebuild and redeploy. The changes should show on http://ejbcahost:8080/ejbca.

Customizing Public Web Pages using ejba-custom

You can use the ejbca-custom feature to override the default files in EJBCA. To customize the Pubic Web pages, modify the style sheets and JSP pages located in modules/publicweb/resources.

Using the ejbca-custom feature, place your override files in an identical file structure in parallel, according to the following example:

ejbca
    modules
        publicweb
ejbca-custom
    modules
        publicweb

When you build using the ant build command, the files in your ejbca-custom directory will override those in the EJBCA distribution, thus making it easy to maintain the changes also when EJBCA is upgraded.