17 Globalization Support

Oracle Adaptive Access Manager 10.1.4.5 has been translated into 26 languages for Adaptive Strong Authenticator and 9 for Adaptive Risk Manager. These translations are bundled along with the English version of the product.

The languages and their locale identifiers are listed below. A locale identifier consists of at least a language identifier, and a region identifier (if required).

Adaptive Risk Manager is translated into French (fr), German (de), Italian (it), Spanish (es), Brazilian Portuguese (pt_br), Japanese (ja), Korean (ko), Simplified Chinese (zh_cn), and Traditional Chinese (zh_tw).

Adaptive Strong Authenticator is translated into 26 languages: French (fr), German (de), Italian (it), Spanish (es), Brazilian Portuguese (pt_br), Japanese (ja), Korean (ko), Simplified Chinese (zh_cn), Traditional Chinese (zh_tw) Arabic (ar), Czech (cs), Danish (da), Dutch (nl), Finnish (fi), Greek (el), Hebrew (iw), Hungarian (hu), Norwegian (no), Polish (pl), Portuguese (pt), Romanian (ro), Russian (ru), Slovak (sk), Swedish (sv), Thai (th), and Turkish (tr).

This chapter provides information on customizing Oracle Adaptive Access Manager for your locale.

17.1 Configuring Language Defaults for Oracle Adaptive Access Manager

Information about the supported locales for a deployment is declared in a user-defined enum named bharosa.locale.enum in the common_enums.properties file.

In the default deployment configuration, there are bharosa.locale.enums defined for the supported locales. For Adaptive Strong Authenticator, 10 languages are enabled.

An example of a bharosa.locale. enum is shown below.

bharosa.locale.enum.german=2
bharosa.locale.enum.german.name=German
bharosa.locale.enum.german.description=German
bharosa.locale.enum.german.language=de
bharosa.locale.enum.german.country=
bharosa.locale.enum.german.adminSupported=true
bharosa.locale.enum.german.enabled=true

In the default deployment configuration, there are bharosa.locale.enums defined for the supported locales.

The common_enums.properties file is located in the <webapps_install_directory>/<webapps_name>/WEB-INF/classes directory.

Use this file to look up the exact property names for the desired locales so that you can add, or add and modify the properties in bharosa_server.properties for Adaptive Risk Manager and bharosa_client.properties for Adaptive Strong Authenticator.

Note:

Do not edit the common_enums.properties file.

To configure language defaults for Oracle Adaptive Access Manager, you will need to perform Steps 1 and 2 for bharosa_server.properties (for Adaptive Risk Manager) and bharosa_client.properties (for Adaptive Strong Authenticator), and then restart the server for the changes to take effect.

Copy the bharosa.local.enum.<locale>.enabled properties of the locales you want to support and ensure they are set to true.
Copy the bharosa.local.enum.<locale>.enabled properties of the locales you do not want to support and ensure they are set to false.
Copy the bharosa.default.locale property and set its value to match the value of the desired locale's bharosa.locale.enum.<locale> property.

Example configuration scenarios are presented below.

17.1.1 Example 1

A German bank wants to set German as the default language and wants to support only German. To do this:

Copy bharosa.locale.enum.german.enabled=true into bharosa_server.properties.
Copy all other bharosa.local.enum.<locale>.enabled properties into bharosa_server.properties and ensure they are set to false.
Copy the bharosa.default.locale property into bharosa_server.properties and set it to the value of the locale enum.

Since bharosa.locale.enum.german=2, set bharosa.default.locale property to 2.
Copy bharosa.locale.enum.german.enabled=true into bharosa_client.properties.
Copy all other bharosa.local.enum.<locale>.enabled properties into bharosa_client.properties and ensure they are set to false.
Copy the bharosa.default.locale property into bharosa_client.properties and set it to 2.
Restart the server for the changes to take effect.

17.1.2 Example 2

A Swiss bank wants to set German as the default, but wants to display in Adaptive Strong Authenticator in all the other languages that Adaptive Strong Authenticator had been translated to. To do this:

Copy bharosa.locale.enum.german.enabled=true into bharosa_server.properties.
Copy all other bharosa.local.enum.<locale>.enabled properties into bharosa_server.properties and ensure they are set to false.
Copy the bharosa.default.locale property into bharosa_server.properties and set it to the value of the locale enum.

Since bharosa.locale.enum.german=2, set bharosa.default.locale property to 2.

Copy the bharosa.locale.enum.<locale>.enabled property into bharosa_client.properties for all the languages Adaptive Strong Authenticator had been translated to and ensure they are set to true.

bharosa.locale.enum.german.enabled=true 
bharosa.locale.enum.italian.enabled=true 
bharosa.locale.enum.french.enabled=true 
bharosa.locale.enum.portuguese_br.enabled=true 
bharosa.locale.enum.spanish.enabled=true
bharosa.locale.enum.korean.enabled=true 
bharosa.locale.enum.chinese_cn.enabled=true 
bharosa.locale.enum.chinese_tw.enabled=true 
bharosa.locale.enum.japanese.enabled=true 
bharosa.locale.enum.arabic.enabled=true 
bharosa.locale.enum.czech.enabled=true 
bharosa.locale.enum.danish.enabled=true 
bharosa.locale.enum.dutch.enabled=true 
bharosa.locale.enum.finnish.enabled=true 
bharosa.locale.enum.greek.enabled=true 
bharosa.locale.enum.hebrew.enabled=true 
bharosa.locale.enum.hungarian.enabled=true 
bharosa.locale.enum.norwegian.enabled=true 
bharosa.locale.enum.polish.enabled=true 
bharosa.locale.enum.portuguese.enabled=true 
bharosa.locale.enum.romanian.enabled=true 
bharosa.locale.enum.russian.enabled=true 
bharosa.locale.enum.slovak.enabled=true 
bharosa.locale.enum.swedish.enabled=true 
bharosa.locale.enum.thai.enabled=true 
bharosa.locale.enum.turkish.enabled=true

Copy the bharosa.default.locale property into bharosa_client.properties and set the value to 2.
Restart the server for the changes to take effect.

17.1.3 Example 3

A French bank wants clients to see French as a default, and wants to support only French, German, English, and Italian. To do this:

Copy the bharosa.locale.enum.<locale>.enabled properties into bharosa_server.properties for French, German, Italian, and English and ensure they are set to true.

bharosa.locale.enum.french.enabled=true
bharosa.locale.enum.german.enabled=true
bharosa.locale.enum.italian.enabled=true
bharosa.locale.enum.english.enabled=true

Copy all other bharosa.local.enum.<locale>.enabled properties into bharosa_server.properties and ensure they are set to false.
Copy bharosa.default.locale property into bharosa_server.properties and set it to the value of the locale enum.

Since bharosa.locale.enum.french=5, set bharosa.default.locale property to 5.
Copy the bharosa.locale.enum.<locale>.enabled properties into bharosa_client.properties for French, German, and Italian and ensure they are set to true.
Copy all other bharosa.local.enum.<locale>.enabled properties into bharosa_client.properties and ensure they are set to false.
Copy bharosa.default.locale property into bharosa_client.properties and set it to 5.
Restart the server for the changes to take effect.

17.2 Adding to the Abbreviation File

Oracle Adaptive Access Manager supports the concept of "fuzzy logic." Fuzzy logic, in part, relies on pre-configured sets of word equivalents, commonly known as abbreviations.

In the English version of Oracle Adaptive Access Manager, there are several thousand English abbreviations (and equivalences). In all other languages, it is necessary for the installer to enhance the brief abbreviation files provided. Without additions to the file, the fuzzy logic will be not as effective.

To add abbreviations:

Open the bharosa_auth_abbreviation_config_<locale>.properties file. The file is located in the <webapps_install_directory>/<webapps_name>/WEB-INF/classes directory.
Add as many abbreviations and equivalences as you want.

There are two different formats you can use:
```
Word=equivalent1
Word=equivalent2
```
or
```
Word=equivalent1,equivalent2, equivalent3
```
For example, in English you can add some of the equivalence for James:
```
Jim=James,\Jamie,\Jimmy
```
With the addition of the equivalences, if a client were to enter a response as Jim, but had originally entered James, Jim would be accepted.

Another example is that "St" may be equivalent to Street.
Restart the server for the changes to take effect.

Note:

Retrieval of abbreviation values is not based on the browser language; values are retrieved from all the bharosa_auth_abbreviation_config_<locale>.properties files.

17.3 Adding Registration Questions

During registration, Oracle Adaptive Access Manager presents customers with three question menus. When a customer registers, he or she is required to select one question from each menu. These three questions become the customer's "registered questions."

To add questions in Oracle Adaptive Access Manager:

Log in to Adaptive Risk Manager
On the Admin menu, point to KBA, point to Questions, and then click Create New Question.
Pick a locale from the list of locales available.
Type the new question in the Question field.

Note:

The deployment administrator must ensure there are enough questions in the database for each of the supported locale as configured in Adaptive Risk Manager during deployment; otherwise, Adaptive Strong Authenticator displays only the English language questions during registration. The number of locale-specific questions must be equal to or greater than the "Questions Per Menu" * "Categories Per Menu" * "Questions User Will Register".

Refer to "KBA Challenge Questions" in the Oracle Adaptive Access Manager Administrator's Guide.

17.4 Configuring Words Used in the Authenticator Caption

During initial registration a user is assigned a word:word pair for their keypad that is generated randomly from word list properties. In English the word:word pairs are in the form, adjective:noun.

In the English version of Oracle Adaptive Access Manager, there are several hundred values in the word lists. In all other languages it is necessary for the installer to enhance the brief word lists provided.

To add words to the word lists:

Open the authentipad_msg_resource_<locale>.properties file. The file is located in the <webapps_install_directory>/<webapps_name >/WEB-INF/classes directory.
Modify the bharosa.user.caption.word1.list and bharosa.user.caption.word2.list properties.
Restart the server for the changes to take effect.

17.5 Configuring "Enter" on the Authenticator Forgot Password Page

A bank wants clients to see "Enter" in its own language on the TextPad's Forgot Password page. To do this:

Open the authentipad_msg_resource_<locale>.properties file. The file is located in the <webapps_install_directory>/<webapps_name >/WEB-INF/classes directory.
Modify the bharosa.uio.default.forgotpassword.primary.page.message= property.
Restart the server for the change to take effect.

17.6 Configuring Tooltip for TextPad's "Enter" Button

A bank wants clients to see "Enter" in its own language for the TextPad's tooltip. To do this:

Open the authentipad_resource_<locale>.properties file. The file is located in the <webapps_install_directory>/<webapps_name >/WEB-INF/classes directory.
Modify the bharosa.authentipad.textpad.enterkey.label=enter property.
Restart the server for the change to take effect.