The parts of Smart ID Digital Access component that end-users can access can be branded, in order to achieve a corporate look-and-feel. Branding and customization can be performed on different levels, ranging from replacing the logotype in the application portal to customizing the appearance of the entire application access procedure: from the software token used for web authentication, through log in pages, and the portal itself.

In Digital Access Admin there is a “Browse” button that leads to a file browser with all files that builds up the portal (the access-point/built-in-files/wwwroot/ folder and sub-folders structure). Copy the files that shall be changed to access-point/custom-files/wwwroot/ within the same file structure before branding starts.

Do not change the original files The reason for this is that changes will be lost when upgrading the system.

Files placed in the …/custom-files/wwwroot/wa folder and sub-folders structure override corresponding files in …/built-in-files/wwwroot/wa folder and sub-folders structure.

These parts of Digital Access component can be branded and customized:

What you can do	How to do it	File name

What you can do	How to do it	File name
Customize colors and fonts in log in pages.	Edit the style sheet for log in pages.	/wa/css/main.css
Customize texts or buttons in log in pages.	Edit individual template files.	Refer to sections below.
Change the logotype in the portal.	Replace the logotype used.	nexus_logo_desktop.svg etc
Customize colors and fonts in the portal.	Edit the application portal style sheet.	themeroller.css and overrides.css

Step by step instructions

Log in to Digital Access Admin with an administrator account.

In the ...branding folder, all texts specific to Digital Access component are collected. These texts can be customized.

In Digital Access Admin, click Browse.
Make sure that all files that should be changed in the access-point/built-in-files/wwwroot/branding directory have been copied to access-point/custom-files/wwwroot/branding.
Modify the appropriate texts in the files described in the table below.
Click Publish to publish the configuration.

Files	Description

Files	Description
authAD.txt	Heading for the Active Directory login page. Appears on every Active Directory template. Note that the other authentication methods are defined by their Display Name and do not need a branding text file.
authselect.txt	Heading for the “Select Authentication Method” page.
authweb.txt	Name of Digital Access component Web when referred in javascript dialogs explaining how to accept the Digital Access component Web ActiveX or java applet.
company.txt	Name of the company. Appears in the application portal.
company_about_url.txt	URL leading to information about the company.
company_contact_url.txt	URL leading to contact information.
copyright.txt	Copyright notice.
portal.txt	Name of the application portal. Appears on the application portal and it’s help page.
product.txt	Name of the product. Appears on the title of each page. product.txt also provide the text to HTML `<title>` tag.

To customize texts and buttons in individual log in pages, there are template files that must be edited. These template files are located in different folders.

Customizing template files requires adequate HTML proficiency.

In Digital Access Admin, click Browse.
Copy the template files from the folder structure in /access-point/built-in-files/wwwroot/wa to the corresponding folder structure in /custom-files/.
Edit any template file that needs to be changed.
Click Publish to publish the customized file.

These are the template files located in access-point/built-in-files/wwwroot/wa.

File name	Description	User variables

File name	Description	User variables
_auto_reauthmessage	Page displayed when the user has to log off and re-authentication is required.
_chooseAuthmech	Page displayed when authentication method is to be selected.	name displayname
_closedown_message	Page displayed when user is timed out from the Access Point.
_deleteLogonCred	Page displayed when password database has been cleared.
_error	Error message displayed to the user.	errmsg
_InternalAuthentication	The Internal Authentication form.	ssodomain ssohost iuid idom
_logoutPage	Page displayed when user has logged off.
_no_session	Page displayed when a session has timed out.
_popup_msg	Page used to display a popup message to the user.	location errmsg
_reauthmessage	Time-out message displayed to user.
_refresh_top	Page displayed when a user needs to refresh the browser.
_securitywarning	Page displayed for security warnings.	errmsg
_TimedoutPage	Page displayed when a user is temporarily locked until a specific time out occurs (currently concerns only SecurID).	auth_timeout
302	Page displayed to redirect the user when a page has moved.	location
302_top	Page displayed to redirect the user when a page has moved.	location
400	Page displayed subsequent to a bad request.
401E	Page displayed subsequent to external authentication failure due to mismatching credentials, if the authentication method on the device is set to Basic authentication.	authmech location
401I	Page displayed subsequent to an internal authentication failure due to mismatching credentials, if the authentication method on the device is set to Basic authentication.
401WIL	Displayed when a user fails to log on using Windows Integrated Login.
403	Page displayed when a client requests a forbidden resource, that is, Access Control denies the resource to be accessed.	eprot ehost uri
404	Page displayed when a requested file on the Access Point does not exist.	eprot ehost file
405	Page displayed when a HTTP-method which is not allowed has been used in a client request.	eprot ehost uri method allow
500	Page displayed when a server error occurs.	errmsg
TestLogonLoginPage	Log in page for TestLogon, that is, when a user requests http://127.0.0.1:19146/ wa/auth?authmech=TestLogon on the local computer where the Access Point is installed.

These are the template files located in access-point/built-in-files/wwwroot/wa/authmech/base.

File Name	Description	User variables

File Name	Description	User variables
GenericForm.html	Base Template for log in forms used in conjunction with Template Specifications of type “GenericForm”. The template specifications form the appearance of the log page for the authentication method by supplying the content of the user variables.	heading errmsg explanation message nolocalstoreText textText textValue readonlyText readonlyValue passwordText checkboxText checkboxValue tokenText oath-newdevice-link reset-password-lin
Dialog.html	Base template used in conjunction with template specifications of type “Dialog”.	heading errmsg explanation message buttonText
Applet.html	Base template used in conjunction with template specifications of type “Applet”.	heading errmsg buttonText
Json,html
SelfServiceForm.html
SelfServiceFormPIN.html
SelfServiceUserChallenge.html
SigningForm.html

Nexus Documentation

Customize and brand Digital Access

Analytics

Step by step instructions

Related content