This appendix provides essential OAAM properties and enums.
It contains the following sections:
OAAM properties are summarized in the following sections.
These properties and default values are used to create the Oracle Access Manager Client Object Pool. These parameters can be configured to higher values if the login volume is high.
Table C-1 Pool Configuration Properties
| Properties | Description |
|---|---|
|
oaam.oam.oamclient.minConInPool |
Defines the minimum number of OAP connections that OAAM will maintain in its pool. It is recommended to keep this value the same as Max Connections as oaam.uio.oam.num_of_connections. |
|
oaam.oam.oamclient.initDelayForWatcher |
Defines the initial delay (in milliseconds) before the OAAM Pool Watcher thread starts to check connections. |
|
oaam.oam.oamclient.periodForWatcher |
Defines the rest period (in milliseconds) for the OAAM Pool Watcher thread, a thread which periodically checks the health of connections in the pool. Keep this a low value, if connections can go bad frequently. |
|
oaam.oam.oamclient.timeout |
Period (in milliseconds) that a request will wait for an available OAP connection before timing out if no connections are available in the pool. Keep this value to a low number. |
|
oaam.uio.oam.num_of_connections |
Primary OAM Server Setting Defines the target (maximum) number of OAP connections to the primary OAM server that OAAM will maintain in its pool. Change default to sufficiently high number. |
|
oaam.uio.oam.secondary.host.num_of_connections |
Secondary OAM Server Setting (if used) Defines the target (maximum) number of OAP connections to the secondary OAM server that OAAM will maintain in its pool. Change default to sufficiently high number. |
Table C-2 Agent Case Properties
Table C-3 Autolearning Properties
Table C-4 Configuration Action Properties
| Properties | Description |
|---|---|
|
Sets the Secure Only flag on any cookies set by OAAM applications directly (does not apply to JSESSIONID). It will mainly apply to the VSC cookie |
Table C-6 Customer Care Properties
| Property | Description |
|---|---|
|
Prints out every SQL if the property is set to zero. |
|
|
oracle.oaam.allentitycache.lifetime.min |
5 This property should not be changed. |
|
oracle.oaam.allentitycache.monitor.sec |
30 This property should not be changed. |
|
oracle.oaam.autolearning.allentities.counts.cache.enabled |
true This property should not be changed. |
Table C-8 lists properties to enable device registration for all applications on the server. To enable on a application specific basis, "default" can be replaced with the appropriate appId in each of the prior property names.
Table C-8 Device Registration Properties
| Properties | Description |
|---|---|
|
Enables device registration. Adds text and a checkbox to the bottom of the challenge page if the property is set to true. When a user is challenged, the checkbox and text would allow him to register the current device (if it is not already registered). If the device is already registered for that user, the option will not appear unless the user unregisters the device in user preferences. |
|
|
bharosa.uio.default.register.questions.registerdevice.enabled |
true Adds device registration to the challenge question registration page. |
|
bharosa.uio.default.register.userinfo.registerdevice.enabled |
true Adds device registration to the Contact Information registration page. |
|
Enables device registration in native integration if property is set to true so that data can be captured. |
Table C-9 Digital Fingerprint Properties
| Properties | Description |
|---|---|
|
Enables use of custom digital fingerprints if you set this property to the type of digital fingerprint you want to capture. For Instance, bharosa.uio.default.device.identification.scheme=applet Note: Flash is set to be the default digital fingerprint in OAAM. |
Table C-10 Encrypted Data Masking Properties
| Properties | Description |
|---|---|
|
Shows the number of characters unmasked. The default length is 3. |
|
|
Shows mask characters to represent encrypted transaction data. For example, set the property to ******** |
|
|
Set to true to enables masking of encrypted transaction data globally. |
|
|
Permissions to enable/disable masking at role level. |
Table C-11 Encryption Properties
Table C-12 Entity and Transaction Properties
| Properties | Description |
|---|---|
|
admin.group.userid.maxlength |
Allows you to increase the maximum length to enter for Login IDs. Default is 255. |
|
admin.group.name.maxlength 255 |
Allows you to increase the maximum length to enter for User IDs. Default is 255. |
|
admin.group.genstring.maxlength |
Allows you to increase the maximum length for Gen String fields. |
Table C-15 Investigation Properties
| Properties | Description |
|---|---|
|
UMS Server Web service URL |
|
|
UMS Server ParlayX Endpoint URL |
|
|
False Configures the use of web service or parlayx API. The value is false by default (Web services recommended). |
|
|
User name for UMS server |
|
|
Password for UMS server |
|
|
UMS authentication policies |
|
|
demo@example.com OAAM from address for OTP messages. |
|
|
bharosa.uio.default.ums.integration.message.status.poll.attempts |
3 Number of times to attempt status poll each time the wait page is displayed. |
|
bharosa.uio.default.ums.integration.message.status.poll.delay |
1000 Delay between status polls while the wait page is being displayed |
|
bharosa.uio.default.ums.integration.sleepInterval |
10000 |
|
3000 |
|
|
2 SMS Challenge enum value |
|
|
SMS Challenge Name of SMS challenge type |
|
|
bharosa.uio.default.challenge.type.enum.ChallengeSMS.description |
SMS Challenge Description of SMS challenge type |
|
bharosa.uio.default.challenge.type.enum.ChallengeSMS.processor |
com.bharosa.uio.processor.challenge.ChallengeSMSProcessor Processor class for SMS challenge type Specifies the java class for handling challenges of this type. The challenge mechanism is customizable through Java classes. See the Oracle Fusion Middleware Developer's Guide for Oracle Adaptive Access Manager for information. |
|
bharosa.uio.default.challenge.type.enum.ChallengeSMS.requiredInfo |
mobile Required fields to challenge user with SMS challenge type A comma separated list of inputs from registration input enum |
|
bharosa.uio.default.challenge.type.enum.ChallengeSMS.available |
Makes available the SMS challenge type Specifies if the challenge type is available for use (service ready and configured). To enable/disable an OTP challenge type, the available flag should be set. |
|
true OTP property for SMS challenge type |
|
|
1 Email Challenge enum value |
|
|
Email Challenge Name of e-mail challenge type |
|
|
bharosa.uio.default.challenge.type.enum.ChallengeEmail.description |
Email Challenge Description of e-mail challenge type |
|
bharosa.uio.default.challenge.type.enum.ChallengeEmail.processor |
com.bharosa.uio.processor.challenge.ChallengeEmailProcessor Processor class for e-mail challenge type Specifies the java class for handling challenges of this type. The challenge mechanism is customizable through Java classes. See the Oracle Fusion Middleware Developer's Guide for Oracle Adaptive Access Manager for information. |
|
bharosa.uio.default.challenge.type.enum.ChallengeEmail.requiredInfo |
Required fields to challenge user with e-mail challenge type A comma separated list of inputs from registration input enum |
|
bharosa.uio.default.challenge.type.enum.ChallengeEmail.available |
false Makes available the e-mail challenge type Specifies if the challenge type is available for use (service ready and configured). To enable/disable an OTP challenge type, the available flag should be set. |
|
true OTP property for e-mail challenge type |
|
|
4 Terms and Conditions enum value |
|
|
Terms and Conditions Name for Terms and Conditions checkbox |
|
|
Terms and Conditions Description for Terms and Conditions checkbox |
|
|
terms HTML input name for Terms and Conditions checkbox |
|
|
checkbox HTML input type for Terms and Conditions checkbox |
|
|
true Required values for Term and Conditions checkbox during registration and user preferences |
|
|
40 HTML input max length for Terms and Conditions checkbox |
|
|
true Required flag for Term and Conditions checkbox during registration and user preferences |
|
|
5 Order on the page for Terms and Conditions checkbox |
|
|
true Enabled flag for Terms and Conditions enum item |
|
|
.+ Regular expression for validation of Terms and Conditions checkbox |
|
|
otp.invalid.terms Error code to obtain error message from if validation of Terms and Conditions fails |
|
|
com.bharosa.uio.manager.user.DefaultContactInfoManager Java class to use to save / retrieve Terms and Conditions from data storage |
|
|
0 Mobile phone enum value |
|
|
Mobile Phone Name for mobile phone field |
|
|
Mobile Phone Description for mobile phone field |
|
|
cell number HTML input name for mobile phone field |
|
|
text HTML input type for mobile phone field |
|
|
15 HTML input max length for mobile phone field |
|
|
true Required flag for mobile phone field during registration and user preferences |
|
|
bharosa.uio.default.userinfo.inputs.enum.mobile.order |
1 Order on the page for mobile phone field |
|
true Enabled flag for mobile phone enum item |
|
|
If configuring through properties:
\\D?(\\d{3})\\D?\\D?(\\d{3})\\D?(\\d{4})
If configuring through OAAM Admin:
\D?(\d{3})\D?\D?(\d{3})\D?(\d{4})
Regular expression for validation of mobile phone field |
|
|
otp.invalid.mobile Error code to obtain error message from if validation of mobile phone entry fails |
|
|
bharosa.uio.default.userinfo.inputs.enum.mobile.managerClass |
com.bharosa.uio.manager.user.DefaultContactInfoManager Java class to use to save / retrieve mobile phone from data storage |
|
2 Mobile phone enum value |
|
|
Mobile Phone 2 Name for mobile phone field |
|
|
bharosa.uio.default.userinfo.inputs.enum.mobile2.description |
Mobile Phone 2 Description for mobile phone field |
|
cell number 2 HTML input name for mobile phone field |
|
|
text HTML input type for mobile phone field |
|
|
15 HTML input max length for mobile phone field |
|
|
true Required flag for mobile phone field during registration and user preferences |
|
|
2 Order on the page for mobile phone field |
|
|
true Enabled flag for mobile phone enum item |
|
|
If configuring through properties:
\\D?(\\d{3})\\D?\\D?(\\d{3})\\D?(\\d{4})
If configuring through OAAM Admin:
\D?(\d{3})\D?\D?(\d{3})\D?(\d{4})
Regular expression for validation of mobile phone field |
|
|
otp.invalid.mobile Error code to obtain error message from if validation of mobile phone entry fails |
|
|
bharosa.uio.default.userinfo.inputs.enum.mobile2.managerClass |
com.bharosa.uio.manager.user.DefaultContactInfoManager Java class to use to save / retrieve mobile phone from data storage |
|
1 Email address enum value |
|
|
Email Address Name for email address field |
|
|
Email Address Description for email address field |
|
|
HTML input name for email address field |
|
|
text HTML input type for email address field |
|
|
40 HTML input max length for email address field |
|
|
true Required flag for email address field during registration and user preferences |
|
|
2 Order on the page for email address field |
|
|
false Enabled flag for email address enum item |
|
|
Regular expression for validation of email address field If configuring through properties:
.+@[a-zA-Z_]+?\\.[a-zA-Z]{2,3}
If configuring through OAAM Admin:
.+@[a-zA-Z_]+?\.[a-zA-Z]{2,3}
|
|
|
otp.invalid.email Error code to obtain error message from if validation of email address entry fails |
|
|
com.bharosa.uio.manager.user.DefaultContactInfoManager Java class to use to save / retrieve email address from data storage |
|
|
bharosa.uio.default.userinfo.inputs.enum.email2 |
2 Email address enum value |
|
Email Address 2 Name for email address field |
|
|
Email Address 2 Description for email address field |
|
|
email2 HTML input name for email address field |
|
|
text HTML input type for email address field |
|
|
40 HTML input max length for email address field |
|
|
true Required flag for email address field during registration and user preferences |
|
|
2 Order on the page for email address field |
|
|
false Enabled flag for email address enum item |
|
|
.+@[a-zA-Z_]+?\\.[a-zA-Z]{2,3} Regular expression for validation of email address field |
|
|
otp.invalid.email Error code to obtain error message from if validation of email address entry fails |
|
|
bharosa.uio.default.userinfo.inputs.enum.email2.managerClass |
com.bharosa.uio.manager.user.DefaultContactInfoManager Java class to use to save / retrieve email address from data storage |
|
Enables/disables the profile registration pages if the OTP channel is enabled and requires registration. |
|
|
Enables/disables the ability to set preferences if the OTP channel is enabled and allows preference setting. User Preferences is a page that allows the user to change their image/phrase, challenge questions, un-register devices, and update their OTP profile. |
|
|
bharosa.uio.default.challenge.type.enum.ChallengeSMS.available |
Enables the Short Message Service (SMS) Challenge Type. This makes it possible for the policies to challenge using OTP via SMS. |
|
Terms and Conditions |
|
|
PLACEHOLDER TEXT FOR TERMS AND CONDITIONS |
|
|
Privacy Policy |
|
|
PLACEHOLDER TEXT FOR PRIVACY POLICY |
Table C-20 Performance Properties
| Properties | Description |
|---|---|
|
bharosa.trackernodehistory.enable |
If the history of the device is not required, then device history logging can be turned OFF by setting the property bharosa.trackernodehistory.enable to false |
|
Controls threshold and logging for rules. By default, the Session Details page does not display the trigger sources if the execution time for alerts is less than 2000 millisecond (2000 ms) since detailed logging is dependent on the execution time. Set this property to 2000. |
|
|
tracker.wf.createHourlyEntries tracker.wf.createDailyEntries |
The Auto-learning feature tracks transactions and authentications being performed by different actors based on patterns you create. This process establishes what is "normal" or average behavior for an individual or a population. By default, Auto-learning collects data for hourly, daily granularity that is not used by the out-of-the-box patterns. If there are no custom patterns that use hourly, daily granular data, then that data collection can be disabled by setting the properties to false. Note: When auto-learning is disabled, no pattern-based risk analysis will be performed. Consider this before you disable auto-learning as the risk analysis may be an important part of your data collection. |
|
vcrypt.tracker.soap.url |
To reduce DNS resolution issues, specify the IP Address of the Oracle Adaptive Access Manager Server where SOAP services are hosted as the value of Oracle Adaptive Access Manager Host in vcrypt.tracker.soap.url property. |
Table C-21 Policies, Rules, and Condition Properties
| Properties | Description |
|---|---|
|
Specifies the checkpoint in which to log the rules. Make sure that "vcrypt.tracker.rules.trace.policySet.XXXXXX" is set to |
|
|
Enables/disables the Action Override feature. This feature is turned off by default. |
| Properties | Description |
|---|---|
|
vcrypt.tracker.ip.detectProxiedIP bharosa.ip.header.name |
Enables use of the "X-Forwarded-For" IP, set this property to true. OAAM does not use the header IP by default. When using OAAM with LBR and SNAT enabled, the client IP address needs to be preserved. This is critical since OAAM relies on the client IP Address when evaluating policies. Make sure the following OAAM properties are set as follows: vcrypt.tracker.ip.detectProxiedIP=true bharosa.ip.header.name=X-Forwarded-For For information on load balancers preserving the Client IP Addresses, see the "Preparing the Network for an Enterprise Deployment" chapter in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management. |
|
Indicates that the application is not protected by the OAAM proxy solution and that OAAM server should not proxy requests for UIO to the OAAM admin system. Set it to true for proxy mode. OAAM Server is configured to be in non-proxy mode with the flag set to false by default. |
Table C-24 SOAP Web Service Access Properties
The account statuses are globalized values. The base definitions are in oaam_core.properties, but the names and descriptions are used from oaam_resources.properties. Overriding the strings would require adding values to a client_resource_locale.properties file in the OAAM Extensions war file.
| Properties | Description |
|---|---|
|
Pending Activation The user started registration, but has not completed it. He has entered his username and password and his information has been stored in the database, but he will not be activated until he has completed registration. The user is available in the system, but he is not yet active and cannot perform any operations. |
|
|
Active The user is active and available in the system. He has completed registration and can perform all operations. |
|
|
Disabled The user is available in the system, but not active. He maybe disabled because of fraud or other reasons and cannot perform any operations. |
|
|
Deleted The user is not available in the system. |
|
|
Invalid The username is not valid. |
The authentication statuses are globalized values. The base definitions are in oaam_core.properties, but the names and descriptions are used from oaam_resources.properties. Overriding the strings would require adding values to a client_resource_locale.properties file in the OAAM Extensions war file.
Table C-26 Authentication Status
| Properties | Description |
|---|---|
|
Success The user is successfully authenticated. |
|
|
Invalid user The username was invalid and not available in the system. |
|
|
Wrong password The user entered the wrong password. The username was entered correctly, but the password was incorrect. |
|
|
Wrong PIN If user has PIN as a password and it was entered incorrectly. |
|
|
Session expired The user logged in to the application then left it inactive for a length of time. When the user tries to use the application again, a message appears telling him the session has expired. The user will have to log in again. |
|
|
Session reused When the session had expired and the user logged in successfully, the status changes from session expired to session reused. |
|
|
User disabled The user was available in the system, but had been disabled in the system for a variety of reasons. The username is valid, but he has been disabled. |
|
|
Pending activation The user has not completed the registration yet. |
|
|
Wrong Answer The user entered the wrong answer to a challenge question. |
|
|
Database Error When user was performing a database operation, he encountered an error. |
|
|
System Error When user was using the application, he encountered an error. |
|
|
Blocked If a user is "Blocked," it is because a policy has found certain conditions to be "true" and is set up to respond to these conditions with a "Block Action." If those conditions change, the user may no longer be "Blocked." The "Blocked" status is not necessarily permanent and therefore may or may not require an administrator action to resolve. For example, if the user was blocked because he was logging in from a blocked country, but he is no longer in that country, he may no longer be "Blocked." |
|
|
Locked "Locked" is the status that Oracle Adaptive Access Manager sets if the user fails a challenge. If the user exceeds the number of retries when attempting to provide a correct answer, then his account becomes "Locked." After that, a Customer Service Representative must reset the status to "Unlocked" before the account can be used to enter the system. |
|
|
Pending The user has logged into the application, completed registration, but the he did not go through the entire flow. |
|
|
auth.status.enum.expired_password.name |
Password Expired The user's password has expired. |
Table C-28 Timezones - Americas, Canada, and Atlantic
| Properties | Description |
|---|---|
|
To set the time zone that will be used for all timestamps in the user interface, use the Property Editor to set For example,
The time zones are as follows: Pacific/Midway (GMT-11:00) Midway - Samoa Time (ST) Pacific/Pago_Pago (GMT-11:00) Pago Pago - Samoa Time (ST) Pacific/Honolulu (GMT-10:00) Honolulu - Hawaii Time (HT) Pacific/Fiji (GMT+12:00) Fiji - Fiji Time (FJT) |
|
|
oaam.adf.timezone |
America/Anchorage (GMT-09:00) Alaska Time (AKT) America/Tijuana (GMT-08:00) Tijuana - Pacific Time (PT) America/Vancouver (GMT-08:00) Vancouver - Pacific Time (Canada) (PT) America/Los_Angeles (GMT-08:00) Los Angeles - Pacific Time (PT) America/Chihuahua (GMT-07:00) Chihuahua - Mexico Time 2 (MT) America/Denver (GMT-07:00) Denver - Mountain Time (MT) America/Edmonton (GMT-07:00) Mountain Time Canada (MT) America/Panama (GMT-05:00) Panama - Eastern Time (ET) America/Montreal (GMT-05:00) Montreal - Eastern Time (Canada) (ET) America/New_York (GMT-05:00) New York - Eastern Time (ET) America/Puerto_Rico (GMT-04:00) Puerto Rico - Atlantic Time (AT) America/Halifax (GMT-04:00) Canada Atlantic Time (AT) America/Santiago (GMT-04:00) Santiago - Chile Time (CLT) America/Caracas (GMT-04:00) Caracas - Venezuela Time (VET) America/Godthab (GMT-03:00) Godthab - Western Greenland Time (WGT) America/Argentina/Buenos_Aires (GMT-03:00) Buenos Aires - Argentine Time (ART) America/Sao_Paulo (GMT-03:00) Sao Paulo - Brasilia Time (BRT) America/St_Johns (GMT-03:30) St Johns - Newfoundland Time (NT) America/Noronha (GMT-02:00) Noronha - Fernando de Noronha Time (FNT) Atlantic/Azores (GMT-01:00) Azores - Azores Time (AZOT) Atlantic/Cape_Verde (GMT-01:00) Cape Verde - Cape Verde Time (CVT) |
Table C-29 Timezones - Europe, Africa, and Atlantic
| Properties | Description |
|---|---|
|
oaam.adf.timezone |
Europe/Dublin (GMT+00:00) Dublin - Greenwich Mean Time (GMT) Europe/London (GMT+00:00) London - Greenwich Mean Time (GMT) Etc/UTC (GMT+00:00) Coordinated Universal Time (UTC) Africa/Casablanca (GMT+00:00) Casablanca - Western European Time (WET) Europe/Lisbon (GMT+00:00) Lisbon - Western European Time (WET) Africa/Nouakchott (GMT+00:00) Nouakchott - Greenwich Mean Time (GMT) Atlantic/Reykjavik (GMT+00:00) Reykjavik - Greenwich Mean Time (GMT) Europe/Prague (GMT+01:00) Prague - Central European Time (CET) Europe/Budapest (GMT+01:00) Budapest - Central European Time (CET) Europe/Madrid (GMT+01:00) Madrid - Central European Time (CET) Europe/Vienna (GMT+01:00) Vienna - Central European Time (CET) Africa/Algiers (GMT+01:00) Algiers - Central European Time (CET) Africa/Lagos (GMT+01:00) Lagos - Western African Time (WAT) Europe/Belgrade (GMT+01:00) Belgrade - Central European Time (CET) Europe/Oslo (GMT+01:00) Oslo - Central European Time (CET) Europe/Rome (GMT+01:00) Rome - Central European Time (CET) Africa/Tunis (GMT+01:00) Tunis - Central European Time (CET) Europe/Stockholm (GMT+01:00) Stockholm - Central European Time (CET) Europe/Copenhagen (GMT+01:00) Copenhagen - Central European Time (CET) Europe/Tirane (GMT+01:00) Tirane - Central European Time (CET) Europe/Zurich (GMT+01:00) Zurich - Central European Time (CET) Europe/Paris (GMT+01:00) Paris - Central European Time (CET) Europe/Berlin (GMT+01:00) Berlin - Central European Time (CET) Europe/Warsaw (GMT+01:00) Warsaw - Central European Time (CET) Europe/Amsterdam (GMT+01:00) Amsterdam - Central European Time (CET) Europe/Brussels (GMT+01:00) Brussels - Central European Time (CET) Europe/Luxembourg (GMT+01:00) Luxembourg - Central European Time (CET) Europe/Bucharest (GMT+02:00) Bucharest - Eastern European Time (EET) |
Table C-30 Timezones - Asia, Europe, and Africa
| Properties | Description |
|---|---|
|
oaam.adf.timezone |
Asia/Nicosia (GMT+02:00) Nicosia - Eastern European Time (EET) Europe/Kiev (GMT+02:00) Kiev - Eastern European Time (EET) Europe/Sofia (GMT+02:00) Sofia - Eastern European Time (EET) Europe/Riga (GMT+02:00) Riga - Eastern European Time (EET) Africa/Johannesburg (GMT+02:00) Johannesburg - South Africa Time (SAT) Europe/Athens (GMT+02:00) Athens - Eastern European Time (EET) Africa/Tripoli (GMT+02:00) Tripoli - Eastern European Time (EET) Africa/Cairo (GMT+02:00) Cairo - Egypt Time (ET) Asia/Beirut (GMT+02:00) Beirut - Eastern European Time (EET) Europe/Tallinn (GMT+02:00) Tallinn - Eastern European Time (EET) Europe/Vilnius (GMT+02:00) Vilnius - Eastern European Time (EET) Europe/Helsinki (GMT+02:00) Helsinki - Eastern European Time (EET) Asia/Amman (GMT+02:00) Amman - Eastern European Time (EET) Asia/Damascus (GMT+02:00) Damascus - Eastern European Time (EET) Africa/Harare (GMT+02:00) Harare - Central African Time (CAT) Asia/Jerusalem (GMT+02:00) Jerusalem - Israel Time (IT) Europe/Istanbul (GMT+02:00) Istanbul - Eastern European Time (EET) Africa/Khartoum (GMT+03:00) Khartoum - Eastern African Time (EAT) Asia/Aden (GMT+03:00) Aden - Arabia Time (AT) Africa/Mogadishu (GMT+03:00) Mogadishu - Eastern African Time (EAT) Asia/Baghdad (GMT+03:00) Baghdad - Arabia Time (AT) Asia/Bahrain (GMT+03:00) Bahrain - Arabia Time (AT) Africa/Djibouti (GMT+03:00) Djibouti - Eastern African Time (EAT) Africa/Nairobi (GMT+03:00) Nairobi - Eastern African Time (EAT) Europe/Moscow (GMT+03:00) Moscow - Moscow Time (MSK) |
Table C-31 Timezones - Europe and Asia
| Properties | Description |
|---|---|
|
oaam.adf.timezone |
Europe/Moscow (GMT+03:00) Moscow - Moscow Time (MSK) Asia/Qatar (GMT+03:00) Qatar - Arabia Time (AT) Asia/Kuwait (GMT+03:00) Kuwait - Arabia Time (AT) Asia/Riyadh (GMT+03:00) Riyadh - Arabia Time (AT) Asia/Tehran (GMT+03:30) Tehran - Iran Time (IRT) Asia/Dubai (GMT+04:00) Dubai - Gulf Time (GT) Asia/Baku (GMT+04:00) Baku - Azerbaijan Time (AZT) Asia/Muscat (GMT+04:00) Muscat - Gulf Time (GT) Asia/Kabul (GMT+04:30) Kabul - Afghanistan Time (AFT) Asia/Yekaterinburg (GMT+05:00) Yekaterinburg - Yekaterinburg Time (YEKT) Asia/Karachi (GMT+05:00) Karachi - Pakistan Time (PKT) Asia/Tashkent (GMT+05:00) Tashkent - Uzbekistan Time (UZT) Asia/Kolkata (GMT+05:30) Kolkata - India Time (IT) Asia/Colombo (GMT+05:30) Colombo - Sri Lanka Time (LKT) Asia/Katmandu (GMT+05:45) Katmandu - Nepal Time (NPT) Asia/Dhaka (GMT+06:00) Dhaka - Bangladesh Time (BDT) Asia/Almaty (GMT+06:00) Almaty - Alma-Ata Time (ALMT) Asia/Novosibirsk (GMT+06:00) Novosibirsk - Novosibirsk Time (NOVT) Asia/Rangoon (GMT+06:30) Rangoon - Myanmar Time (MMT) Asia/Krasnoyarsk (GMT+07:00) Krasnoyarsk - Krasnoyarsk Time (KRAT) Asia/Ho_Chi_Minh (GMT+07:00) Ho Chi Minh - Indochina Time (ICT) Asia/Jakarta (GMT+07:00) Jakarta - West Indonesia Time (WIT) Asia/Bangkok (GMT+07:00) Bangkok - Indochina Time (ICT) Asia/Kuala_Lumpur (GMT+08:00) Kuala Lumpur - Malaysia Time (MYT) |
Table C-32 Timezones - Asia, Australia, Pacific, Etc
| Properties | Description |
|---|---|
|
oaam.adf.timezone |
Asia/Kuala_Lumpur (GMT+08:00) Kuala Lumpur - Malaysia Time (MYT) Asia/Shanghai (GMT+08:00) Shanghai - China Time (CT) Asia/Taipei (GMT+08:00) Taipei - China Time (CT) Asia/Irkutsk (GMT+08:00) Irkutsk - Irkutsk Time (IRKT) Asia/Singapore (GMT+08:00) Singapore - Singapore Time (SGT) Asia/Hong_Kong (GMT+08:00) Hong Kong - Hong Kong Time (HKT) Asia/Manila (GMT+08:00) Manila - Philippines Time (PHT) Australia/Perth (GMT+08:00) Perth - Western Time (Australia) (WT) Asia/Yakutsk (GMT+09:00) Yakutsk - Yakutsk Time (YAKT) Asia/Tokyo (GMT+09:00) Tokyo - Japan Time (JT) Asia/Seoul (GMT+09:00) Seoul - Korea Time (KT) Australia/Adelaide (GMT+09:30) Adelaide - Central Time (South Australia) (CT) Australia/Darwin (GMT+09:30) Darwin - Central Time (Northern Territory) (CT) Asia/Vladivostok (GMT+10:00) Vladivostok - Vladivostok Time (VLAT) Pacific/Guam (GMT+10:00) Guam - Chamorro Time (ChT) Australia/Hobart (GMT+10:00) Hobart - Eastern Time (Tasmania) (ET) Australia/Sydney (GMT+10:00) Sydney - Eastern Time (New South Wales) (ET) Australia/Brisbane (GMT+10:00) Brisbane - Eastern Time (Queensland) (ET) Asia/Magadan (GMT+11:00) Magadan - Magadan Time (MAGT) Pacific/Auckland (GMT+12:00) Auckland - New Zealand Time (NZT) Pacific/Fiji (GMT+12:00) Fiji - Fiji Time (FJT) Asia/Kamchatka (GMT+12:00) Kamchatka - Petropavlovsk-Kamchatski Time (PETT) Etc/GMT-12 (GMT+12:00) Dateline Standard Time (UTC+12:00) Pacific/Tongatapu (GMT+13:00) Tongatapu - Tonga Time (TOT) |
Table C-33 User Interface Properties
| Properties | Description |
|---|---|
|
Specifies the user name to be in lowercase if set to false By default this property is set to true. When it is set to true, the user name is always in lower case. If it is set to false, the user name is taken as is. For example:
If property is true (default), all of these are the same user and will appear in the OAAM Administration Console as "myusername". If property is false, all of these are different users and will appear in the OAAM Administration Console as entered. |
|
|
Limits the maximum row selection for exporting a report of the results to Microsoft Excel. Reports are the results from the Search pages for policies, questions, validations, snapshots, properties, entities, transactions, conditions, groups, patterns, and so on. |
|
|
Search screen default time range. |
|
|
Session screen default time range. |
Table C-34 Virtual Authentication Device Properties
This section contains the following topics:
In this example, "myStatus" is the status that is being created. Other than the first line which specifies customercare.case.status.enum. myStatus is 100, all others are properties of this enum element.
Table C-35 New Status Enumeration
| Properties | Description and Values |
|---|---|
|
100 Specify a number that is not used by an existing case status enum |
|
|
myStatus The status name |
|
|
myStatus A description of the status |
|
|
1,2,3,4,5,8,9,10,11,102,103 Enum numbers for case.action.enum that tells the system which actions can be performed on the case in this state |
|
|
oaam.perm.view.case.status.new Enum for the access permission for this case status (who can access the case in this state) |
|
|
12 Specify an order number that will be used in the display when the case status is displayed in various drop down menus |
|
|
true Specify whether the status is displayed in the interface. If you do not want this status to be displayed in the user interface, then set this to false |
|
|
customercare.case.statuschange.message.enum List of messages that you can see on screen when the status changes |
|
|
customercare.case.statuschange.new.notes.enum List of canned notes that you can see for this status. If you are defining a new status, define your new notes enum. For instructions, refer to the "Adding Canned Notes to Case Status" section. |
To add new alert levels add the enum element for the alert level. An example for adding an "ultralow" alert level is shown below.
Table C-36 New Alert Level Enumeration
| Property | Description and Value |
|---|---|
|
20000 Specify a number not used by alerts |
|
|
ALERT_ULTRA_LOW Name of the alert level |
|
|
Ultra Low Label that will be used in user interface |
|
|
Ultra Low alert Description of the alert level |
|
|
Magenta Color to display on session |
|
|
Cyan Color to display on alert screen |
|
|
23 Order to display in the drop down menu |
When you add a new status to case status, you should define the New Notes enum as defined on this first line below and then add note options to that enum. Those options will appear as canned notes. Note that you must configure the enum name as a note enum in the new status enum element that you defined.
Table C-37 Adding Canned Notes Enumeration
When you add a case severity enum you will need to define the corresponding properties for it. A sample of a "superhigh" severity enum is shown below.
customercare.case.severity.enum.superhigh=4 // Number that is not used by existing severity enum element. customercare.case.severity.enum. superhigh.name=Super High //Name customercare.case.severity.enum. superhigh.description=Super High Severity level // some description customercare.case.severity.enum. superhigh.image=flag_lg_h.gif // Image file for the icon that displays the severity customercare.case.severity.enum. superhigh.access=oaam.perm.view.case.severity.high // Access permission to view the cases of high severity // define new if you do not want to resuse the enum customercare.case.severity.enum. superhigh.order=3 // Order in the drop down menu displays customercare.case.severity.enum. superhigh.display=true // Whether to display on user interface or not customercare.case.severity.enum. superhigh.messagelist=customercare.case.severitychange.message.enum // Message to be given when severity change is done customercare.case.severity.enum. superhigh.notelist=customercare.case.severitychange.high.notes.enum // Canned notes when severity change to this severity happens. You may want to define new here.
By default the Auto Change of Case Status is enabled. The property is as follows:
customercare.case.autostatuschange.enum.flowone.enabled=true
To disable Auto Change of Case Status set the following parameter:
customercare.case.autostatuschange.enum.flowone.enabled=false
Configurable actions create cases with a status of New. When the case is opened, the status is changed to Pending.
These cases change from New to Pending automatically on access. The default setting are as follows:
customercare.case.autostatuschange.enum.flowone=1 customercare.case.autostatuschange.enum.flowone.name=Flow onecustomercare.case.autostatuschange.enum.flowone.description=Status flow onecustomercare.case.autostatuschange.enum.flowone.enabled=true customercare.case.autostatuschange.enum.flowone.from=new customercare.case.autostatuschange.enum.flowone.to=pending
Escalated cases have a Case Status of Escalated. When the case is opened, the status is changed to Pending.
These cases change from Escalated to Pending automatically on access. The default settings are as follows:
customercare.case.autostatuschange.enum.flowtwo=2 customercare.case.autostatuschange.enum.flowtwo.name=Flow Two customercare.case.autostatuschange.enum.flowtwo.description=Status flow two customercare.case.autostatuschange.enum.flowtwo.enabled=true customercare.case.autostatuschange.enum.flowtwo.from=escalated customercare.case.autostatuschange.enum.flowtwo.to=pending customercare.case.autostatuschange.enum.flowtwo.casetype=agent
The default setting is for CSR cases to expire after 24 hours. After a CSR case expires, a CSR cannot access them. CSR Managers have to extend the expiration time so that the CSR can access them.
The properties for setting and disabling expiry behavior are provided below.
To disable the expiry behavior for CSR cases, modify the following property:
customercare.case.expirybehavior.enum.csrcase.behavior = none
Note:
You do not need to change the other parameters.To set expiry behavior for CSR cases (default setting), modify the following properties:
customercare.case.expirybehavior.enum.csrcase.behavior = expiry customercare.case.expirybehavior.enum.csrcase.label = Expired customercare.case.expirybehavior.enum.csrcase.durationInHrs = 24 customercare.case.expirybehavior.enum.csrcase.resetonaccess = false
Agent Cases have a default expiration date of 24 hours from the date of creation.
Information to change the default behavior is provided below.
To disable the expiry behavior for Agent cases, modify the following property as shown below.
customercare.case.expirybehavior.enum.agentcase.behavior = none
To set expiry behavior for Agent cases, modify the following properties as shown below.
Note:
You will not need to change the other parameters.customercare.case.expirybehavior.enum.agentcase.behavior = expiry customercare.case.expirybehavior.enum.agentcase.label = Expired customercare.case.expirybehavior.enum.agentcase.durationInHrs = 24 customercare.case.expirybehavior.enum.agentcase.resetonaccess = false
By default only Investigators and Investigation Managers have access to create Agent cases. The property for investigator access is oaam.permission.creatagentcase=oaam.perm.create.case.type.agent
To give a CSR access to Agent cases, configure the property as follows: oaam.permission.creatagentcase=oaam.perm.create.case.type.csr
After setting the property, the CSR has full access to create agent cases.