To customize the error pages, determine whether you need one custom file or multiple files:
If you do not need to support multiple languages, create one custom file for all customized messages.
If you need to support multiple languages, create a custom file for each language you want to customize.
Create the custom properties file and name it:
To support one language, name the file as nidp_custom_resources.properties.
To support multiple languages, create a nidp_custom_resources_<le_cy>.properties file for each supported language. Replace <le_cy> with the standard convention for Java Resource Bundles for the language or the language and country. For example:
nidp_custom_resources_en_US.properties nidp_custom_resources_fr.properties nidp_custom_resources_es.properties
If you want to support a custom messages for a language and a country and for just the language, you must create two files. For example:
nidp_custom_resources_es_VE.properties nidp_custom_resources_es.properties
Download the nidp.jar file from /opt/novell/nids/lib/webapp/WEB-INF/lib. For information about how to download a file, see Downloading Files from a Server.
Unzip the nidp.jar file in your working directory and locate the properties files in the following directories:
com/novell/nidp/resource/strings com/novell/nidp/resource/logging com/novell/nidp/resource/jsp com/novell/nidp/resource/jcc com/novell/nidp/resource/noxlate com/novell/nidp/liberty/wsf/idsis/ppservice/model com/novell/nidp/liberty/wsf/idsis/epservice/model com/novell/nidp/liberty/wsf/idsis/opservice/model com/novell/nidp/liberty/wsf/idsis/apservice/model com/novell/nidp/liberty/wsf/interaction com/novell/nidp/liberty/wsf/idsis/ssservice/model com/novell/nidp/servlets/handler/identityeditor com/novell/nidp/servlets/handler/identityaccesseditor com/novell/nidp/liberty/wsf/idsis/model com/novell/nidp/liberty/wsf/idsis/authority/ldap/attribute/plugins/resources com/novell/nidp/liberty/wsf/idsis/ldapservice/model
The localized properties files contain messages that end users might see. The properties files that have not been localized contain messages that the end users must not see.
Locate the messages you want to customize and copy them to your custom file.
All messages that you want to customize are placed in this file, even though they come from different properties files.
Your file must look similar to the following if you selected to customize messages from the nidp_resources_en_US.properties file and the SSModelResources_en_US.properties file:
NIDPMAIN.100=An Identity Provider response was received that failed to authenticate this session. NIDPMAIN.101=A request for identity federation could not be completed. NIDPMAIN.102=A request for identity federation termination could not be completed. SS.WKSLdapCreds = LDAP Credentials SS.WKSELdapCredsUserName = LDAP User Name SS.WKSELdapCredsUserDN = LDAP User DN SS.WKSELdapCredsUserPassword = LDAP Password SS.WKSX509Creds = X509 Credentials
(Conditional) If multiple languages are supported, copy messages to each custom language file.
Replace the messages in the file with your custom messages.
Replace the string after the equals (=) sign with your translated or customized message.
If you are using double-byte characters, the characters need to be in Unicode, hexadecimal format with a \u prefix. For example: \u5c71.
Save the file.
Add the custom properties files to the /opt/novell/nam/idp/webapps/nidp/WEB-INF/classes folder of the appropriate Identity Server cluster using Advanced File Configurator. For more information, see Adding Configurations to a Cluster.
(Optional) Enable debug logging to enable messages for loading the custom properties files:
Click Devices > Identity Servers > Edit > Auditing and Logging.
In the Component File Logger Levels section, select Debug level for Application.
Click OK, and update Identity Server.
(Optional) To verify the loading of the custom properties files, perform the following steps:
View the log file by clicking Auditing > General Logging.
Search for messages similar to the following in catalina.out:
The named Custom Properties File was loaded and will be used: Custom Properties File successfully loaded! Name: <Custom Properties FileName> An error occurred loading a specific Custom Properties File. Loading of other Custom Properties Files will continue. <Error Description>, Attempting to load Custom Properties File! Name: <Custom Properties FileName> The locale specifier in the Custom Properties File filename could not be successfully parsed into a valid locale. Loading of other Custom Properties Files will continue. Custom Properties File load failed. Could not determine correct locale! Name: <Custom Properties FileName> A general error occurred loading Custom Properties Files. Loading will stop and all un-loaded Custom Properties Files will not be loaded. <Error Description>, Attempting to load Custom Properties Files!