This appendix provides essential OAAM properties and enums.
It contains the following sections:
About Adding User Defined Enum Elements or Changing the Enabled Attribute of an Enum Element
Access Manager and Oracle Adaptive Access Manager Integration Properties
Oracle Identity Manager and Oracle Adaptive Access Manager Integration Properties
The creation of any new user defined enum element or changing the enabled
attribute of an enum element from false
to true
will require a restart of the managed servers.
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. |
The following properties are used to configure the number of questions presented in the Forgot Password flow. Times to challenge is based on the checkpoint and challenge type. Post Authentication defaults to 1 and Forgot Password defaults to number of configured challenge questions which defaults to 3.
Table C-2 Forgot Password Flow Properties
Properties | Description |
---|---|
bharosa.uio.default.postauth.ChallengeQuestion.timestochallenge |
1 |
bharosa.uio.default.ForgotPassword.ChallengeQuestion.timestochallenge |
3 |
bharosa.uio.default.ForgotPassword.ChallengeEmail.timestochallenge |
1 |
bharosa.uio.default.ForgotPassword.ChallengeSMS.timestochallenge |
1 |
bharosa.uio.default.ForgotPassword.ChallengeIM.timestochallenge |
1 |
bharosa.uio.default.ForgotPassword.ChallengeVoice.timestochallenge |
1 |
Table C-3 Agent Case Properties
Properties | Description |
---|---|
oaam.customercare.agent.case.allow.userinfo |
Turns on/off user information for Agent case, which are not in the Escalated status. When an OAAM Agent Case is autogenerated from the Configurable Action, the User Details panel is populated with user details for the session for which the case was created. When manually creating a case and linking to a session, user details can be populated. As a result, subsequent searches of cases by Username or User ID can locate manually created cases. The Agent case creation page can optionally accept entry of a valid Username and/or User ID if the |
oaam.admin.investigator.default.landing.page |
customercare Changes the landing page to either Cases, Sessions or Search Transactions. |
oaam.admin.investigator.landing.page2 |
sessions Changes the landing page to either Cases, Sessions or Search Transactions. |
oaam.admin.investigator.landing.page3 |
transactionlogs Changes the landing page to either Cases, Sessions or Search Transactions. |
Table C-4 Autolearning Properties
Properties | Description |
---|---|
vcrypt.tracker.autolearning.enabled |
Enables/disables the autolearning feature. This property must always be set to |
vcrypt.tracker.autolearning.use.auth.status.for.analysis |
Enables/disables the authentication patterns. Authentication patterns are the patterns that analyze the data related to authentication (login) related information only. You can set it to True or False. |
vcrypt.tracker.autolearning.use.tran.status.for.analysis |
Enables the transaction-related patterns. Set to true for the transaction-related patterns to work. Transaction related patterns analyze the transaction related data for autolearning. An example is a pattern that profiles users who are performing wire transfer operations. |
oracle.oaam.transactions.analyzepatterns |
Enables the collection of pattern data for transactions. Set to true for pattern data to be collected for transactions. |
vcrypt.bharosa.autolearning.numPriorities |
Creates the number of thread pools as the number of priorities. These thread pools are used for post processing the autolearning data. This number should be more than 1. |
vcrypt.bharosa.autolearning.threadMultiplier |
Create the number of threads for post processing. These threads are part of the thread pool that is used for post processing autolearning data. Keep this number to at least 5. |
vcrypt.tracker.autolearnin.enabled |
Controls the status for the product level. Setting the value to false disables some of the post processing for autolearning. Rules continue to run but may be using stale data. |
vcrypt.tracker.autolearning.use.auth.status.for.analysis |
Enables/disables autolearning post processing if you do not want to change the client code. Setting this property to true results in autolearning processing for the authentication type of updateAuthStatus requests if the status is SUCCESS for that authentication request. However if the status is not SUCCESS, autolearning does not occur. Running autolearning rules with this property set to false runs the rules on the data that is stale. If this property is set to false and autolearning rules are running, and if the log level is set to "debug" for "com.bharosa.vcrypt.tracker.rules.impl.VCryptTrackerAutoLearningImpl" class; then a message is written to the log saying that this property is disabled and rules are still being run. Use this property when the client code does not explicitly call the autolearning API. |
oracle.oaam.transactions.analyzepatterns |
Enables/disables the collection of pattern data for transactions. Set to true for pattern data to be collected for transactions. |
vcrypt.tracker.autolearning.use.tran.status.for.analysis |
Enable this property if you want autolearning (post processing) to occur but do not want to change the client code. Setting this property to true results in autolearning processing for updateTransactionStatus requests if the status is SUCCESS for that transaction request. However if the status is not SUCCESS, autolearning does not occur. Running autolearning rules with this property set to false runs the rules on the data that is stale. If this property is set to false and you have autolearning rules running, and if the log level is set to "debug" for the "com.bharosa.vcrypt.tracker.rules.impl.VCryptTrackerAutoLearningImpl" class; a message is written to the log saying that this property is disabled and rules are still running. |
vcrypt.tracker.autolearning.use.synchronous.execution.for.pattern.analysis |
Controls whether the pattern analysis occurs in synchronous mode. If set to true, pattern analysis is performed synchronously. The updateAuthStatus or updateTransactionStatus call may take longer to complete since all the pattern data update occurs as part of the same updateStatus call. |
vcrypt.tracker.autolearning.update.entity.profile.for.auth.patterns |
Enables/disables update of profiles for entities as part of pattern analysis. |
bharosa.menu.queries.entities |
Determines whether the menu item to view historical data should be shown in the OAAM Administration Console. |
bharosa.arm.pagetitle.queries.entities.patternworkflow |
Default location of the menu for the pattern historical data. Use this historical data page to check to see whether pattern data collection is functioning properly. |
Table C-5 Configuration Action Properties
Properties | Description |
---|---|
dynamicactions.enabled |
Enables the configurable actions feature if set to true. |
com.bharosa.vcrypt.tracker.dynamicactions.impl.CaseCreationAction |
Create case action |
com.bharosa.vcrypt.tracker.dynamicactions.impl.AddToListConfigurableAction |
Add to list action |
Properties | Description |
---|---|
oaam.cookies.secure |
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-7 Customer Care Properties
Properties | Description |
---|---|
bharosa.uio.default.username.case.sensitive |
If set to true, the user name will be stored as typed into the User Name field when creating CSR cases. The user name is case sensitive. If set to false, the user name will be in lower case regardless of the actual case that was typed into the User Name field when creating CSR cases. |
customercare.case.expirybehavior.enum.csrcase.behavior |
expiry Sets expiry behavior for CSR cases |
customercare.case.expirybehavior.enum.csrcase.label |
Expired Sets expiry behavior for CSR cases |
customercare.case.expirybehavior.enum.csrcase.durationInHrs |
24 Sets expiry behavior for CSR cases |
customercare.case.expirybehavior.enum.csrcase.resetonaccess |
false Sets expiry behavior for CSR cases |
customercare.case.expirybehavior.enum.csrcase.behavior |
none Disables the expiry behavior for CSR cases |
oaam.permission.creatagentcase |
oaam.perm.create.case.type.csr Allows investigator access to create Agent cases |
customercare.case.actiontype.enum.accesscase.description |
The values for the Notes column in the Logs tab for notes that are not added by the user will appear in English by default. The notes are taken from the action enums "note" field (property).The value of that property is saved into database (as notes). After it is saved, users cannot change that data. Implementations can customize the "note" in the enum property to the localized value. "Access case" is inside the customercare.case.actiontype.enum.accesscase.description=Access case Case creation / access logic will use that string for the creating records after that point. |
customercare.case.expirybehavior.enum.agentcase.behavior |
none Disables the "overdue/expiry" behavior for Agent cases overdue Sets "expiry/overdue" behavior for Agent cases |
customercare.case.expirybehavior.enum.agentcase.label |
Overdue Sets "expiry/overdue" behavior for Agent cases |
customercare.case.expirybehavior.enum.agentcase.durationInHrs |
24 Sets "expiry/overdue" behavior for Agent cases |
customercare.case.expirybehavior.enum.agentcase.resetonaccess |
true Sets "expiry/overdue" behavior for Agent cases |
customercare.case.autostatuschange.enum.flowone.enabled |
Enables Auto Change of Case Status if set to true. Disables Auto Change of Case Status if set to false. |
customercare.case.autostatuschange.enum.flowone customercare.case.autostatuschange.enum.flowone.name onecustomercare.case.autostatuschange.enum.flowone.description onecustomercare.case.autostatuschange.enum.flowone.enabled customercare.case.autostatuschange.enum.flowone.from customercare.case.autostatuschange.enum.flowone.to |
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 Configurable actions create cases with a status of "New". When the case is opened, the status is changed to "Pending." For these cases to change from "New" to "Pending" automatically on access, the properties are configured by default to the values. |
customercare.case.autostatuschange.enum.flowtwo customercare.case.autostatuschange.enum.flowtwo.name customercare.case.autostatuschange.enum.flowtwo.description customercare.case.autostatuschange.enum.flowtwo.enabled customercare.case.autostatuschange.enum.flowtwo.from customercare.case.autostatuschange.enum.flowtwo.to customercare.case.autostatuschange.enum.flowtwo.casetype |
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 Escalated cases have a Case Status of Escalated. When the case is opened, the status is changed to "Pending". For cases to change from Escalated to Pending automatically on access, the properties are configured by default. |
oaam.comparetrx.max.rows.allowed |
oaam.comparetrx.max.rows.allowed=10 Limits the number of transaction rows selected for Compare Transaction. |
oaam.generic.idmshellrhs.tab.width |
oaam.generic.idmshellrhs.tab.width=400 IDM shell right hand side width |
oaam.customercare.linksessions.max.rows.allowed |
oaam.customercare.linksessions.max.rows.allowed=25 Limits the number of session rows to be linked to agent case. |
oaam.admin.investigator.default.landing.page oaam.admin.investigator.landing.page2 oaam.admin.investigator.landing.page3 oaam.admin.investigator.landing.showhometab |
oaam.admin.investigator.default.landing.page=customercare oaam.admin.investigator.landing.page2=sessions oaam.admin.investigator.landing.page3=transactionlogs oaam.admin.investigator.landing.showhometab=false Default landing page for the investigator |
oaam.admin.csr.default.landing.page |
oaam.admin.csr.default.landing.page=customercare Default landing page for the CSR; points to the taskflowId(oaam.menu.enum) |
oaam.utility.max.filter.items.allowed |
oaam.utility.max.filter.items.allowed=15 Maximum filter items under tagged panel |
oaam.utility.filter.isconjuctionall |
oaam.utility.filter.isconjuctionall=true Utility filter items conjunction type (all or any) |
oaam.utility.filter.timerange.default |
oaam.utility.filter.timerange.default=oneday Utility filter default time-range: oaam.session.filter.timerange.enum |
oaam.customercare.agent.case.allow.userinfo |
oaam.customercare.agent.case.allow.userinfo=false Turns on/off user information for Agent case (which is not in escalated status) |
customercare.case.agent.landingtf.access customercare.case.csr.landingtf.access |
customercare.case.agent.landingtf.access=oaam.perm.do.case.agent.landingtf customercare.case.csr.landingtf.access=oaam.perm.do.case.csr.landingtf High-level permissions for landing pages for CSR and Investigator |
bharosa.multitenant.boolean |
Turns on the access control in the OAAM Administration Console for multitenant deployments, you must set the bharosa.multitenant.boolean property to true. By default, the value is set to false. |
Property | Description |
---|---|
bharosa.db.query.performance.warning.threshold.ms |
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-9 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-9 Device Registration Properties
Properties | Description |
---|---|
bharosa.uio.default.registerdevice.enabled |
Enables device registration. Adds text and a check box to the bottom of the challenge page if the property is set to true. When a user is challenged, the check box 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. |
bharosa.uio.default.userpreferences.unregister.this.enabled |
Enables user to be able to unregister current device in user preferences. |
bharosa.uio.default.userpreferences.unregister.all.enabled |
Enables user to be able to unregister all devices in user preferences |
bharosa.tracker.send.devideId |
Enables device registration in native integration if property is set to true so that data can be captured. |
Table C-10 Digital Fingerprint Properties
Properties | Description |
---|---|
bharosa.uio.default.device.identification.scheme |
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-11 Encrypted Data Masking Properties
Properties | Description |
---|---|
oaam.transaction.encrypted.data.mask.suffix.length |
Shows the number of characters unmasked. The default length is 3. |
oaam.transaction.encrypted.data.mask.char |
Shows mask characters to represent encrypted transaction data. For example, set the property to ******** |
oaam.transaction.encrypted.data.mask |
Set to true to enables masking of encrypted transaction data globally. |
<permission> <class>oracle.adf.share.security.authorization.RegionPermission</class> <name>oaam.transaction.encrypted.data.unmask.perm</name> <actions>view</actions> </permission> |
Permission to enable/disable masking at role level. |
Table C-12 Encryption Properties
Property | Description |
---|---|
bharosa.cipher.encryption.algorithm.system.default |
Switches to different encryption types |
keystorepasswd |
Password for opening the keystore. |
keystorealiaspasswd |
Password reading alias (key) in the keystore |
keyFile |
keyFile=soap_key.file File containing from key. Please note, keys in AES could be binary. Also note algorithms like 3DES require minimum 24 characters in the key |
keystorefilename |
keystorefilename=system_soap.keystore Keystore file name. |
keystorealias |
keystorealias=vcrypt.soap.call.passwd This is the keystore alias. |
vcrypt.soap.auth.keystorePassword=<base64 encoded keystore password> vcrypt.soap.auth.aliasPassword=<based64 encoded password to the alias> vcrypt.soap.auth.username=<user configured for accessing the soap services> vcrypt.soap.auth.keystoreFile=system_soap.keystore |
Properties with the encoded passwords and the authentication user name to add to |
Table C-13 Entity and Transaction Properties
Properties | Description |
---|---|
bharosa.trackeradmin.show.transaction.detail |
Enables you to view transactions in the Session Details page if set to true. Turns off the display for transactions is set to false. |
oaam.admin.detail.ip.enabled oaam.admin.detail.user.enabled oaam.admin.detail.device.enabled oaam.admin.detail.fingerprint.enabled oaam.admin.detail.alert.enabled oaam.admin.detail.challengecount.enabled |
Enables you to be able to use the details pages. |
oaam.transaction.mapping.startindex.min |
Starts the substring operation from the first character of the string if you set this property to |
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-16 Integration Properties
Properties | Description |
---|---|
oaam.uio.oam.integration.stepup.enabled |
Disables the Step-up use case in Access Manager-OAAM TAP integration, you must set the property to false. |
oaam.server.integration.app_id.param |
Configures the HTTP request parameter key that the integration processor will use to try to read AppId from when entering OAAM entry point. Access Manager, for example, can be set up to send an AppId via the challenge URL. This allows for the key to be customized.
would allow it to be sent as
|
Table C-17 Investigation Properties
Properties | Description |
---|---|
bharosa.trackeradmin.show.transaction.detail |
Set to true to be able to view transactions in the Session Details page. Setting the property to false turns off the display for transactions. |
oaam.customercare.agent.case.allow.userinfo |
Turns on/off user information display for Agent case (which is not in escalated status |
oaam.admin.investigator.default.landing.page=customercare oaam.admin.investigator.landing.page2=sessions oaam.admin.investigator.landing.page3=transactionlogs |
Changes the landing page to either Cases, Sessions or Search Transactions with the use of property |
incrementCacheCounter |
Set to true in the rule.action.enum so that different actions performed by the user along with the aggregate count for each one of them is available in the user details: profile data. |
oaam.xls.case.linkedsession.export.row.upperbound |
The maximum number of linked session allowed to be exported is pre-configured for 1000. To change the limit, edit this configurable property. |
Properties | Description |
---|---|
bharosa.kba.active |
Enables KBA if set to true. |
bharosa.config.type.kba_config.enum.regQuestionsCount.validation.minValue bharosa.config.type.kba_config.enum.regQuestionsCount.validation.maxValue |
Specifies the maximum and minimum limits for questions the user will register. bharosa.config.type.kba_config.enum.regQuestionsCount.validation.minValue=3 bharosa.config.type.kba_config.enum.regQuestionsCount.validation.maxValue=7 The setting should be between 3 and 7 to offer security but not over burden a user's memory. The basic industry standard for KBA is 3 registered questions. |
challenge.question.registration.groups.minimum.questions.per.category.count challenge.question.registration.groups.categories.count challenge.question.registration.groups.questions.count challenge.question.registration.groups.count challenge.question.registration.groups.maxlimit |
Controls the listing of questions in the OAAM server. challenge.question.registration.groups.minimum.questions.per.category.count =1 challenge.question.registration.groups.categories.count=5 challenge.question.registration.groups.questions.count=5 challenge.question.registration.groups.count=3 challenge.question.registration.groups.maxlimit=5 |
bharosa.config.type.kba.config.enum.maxCategoryPerMenuCount.property_name |
Controls the minimum number of questions in a category that must exists before changes can be made to a question in the category. The default is 5. You cannot edit questions in a category if the number of questions in the category is below the minimum. For example, you cannot change the locale for a question unless there are at least 5 other questions for that locale in that category. |
Table C-21 Offline Scheduler Properties
Properties | Description |
---|---|
vcrypt.reports.scheduler.activate |
Enables/disables scheduler so that jobs are run. By default, the property is set to false. Jobs can be created, but they will not run until the property is changed to true. |
bharosa.ra.loadrun.resetbeforerun |
Performing a Load and Run job multiple times appends rule data to existing sessions, resulting in duplicate checkpoints for each time the job is performed. If you want old checkpoint data to be erased before checkpoint rules are run, ensure that |
oaam.admin.detail.mobile.enabled=true |
By default, the Client-Application and Latitude and Longitude attributes are not displayed in the Session Details page in the OAAM Offline whereas they are displayed in the same page in OAAM Admin. To display these attributes in the Session Details page, add the oaam.admin.detail.mobile.enabled=true property to the oaam_admin.properties file of the offline server |
Property | Default Value | Description |
---|---|---|
bharosa.uio.default.register.userinfo.enabled |
Setting the property to true enables the profile registration pages if the OTP channel is enabled and requires registration. |
|
bharosa.uio.default.userpreferences.userinfo.enabled |
Setting the property to true enables the user 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.ChallengeEmail.available |
false |
Availability flag for email challenge type |
bharosa.uio.default.challenge.type.enum.ChallengeSMS.available |
false |
Availability flag for SMS challenge type |
bharosa.uio.default.challenge.type.enum.ChallengeIM.available |
false |
Availability flag for instant message challenge type |
bharosa.uio.default.ums.integration.webservice |
UMS Server Webservice URL
|
|
bharosa.uio.default.ums.integration.parlayx.endpoint |
UMS Server ParlayX Endpoint URL
|
|
bharosa.uio.default.ums.integration.useParlayX |
false |
Configures the use of webservice or parlayx API. The value is false by default (Webservices recommended) |
bharosa.uio.default.ums.integration.userName |
Username for Oracle User Messaging Service server |
|
bharosa.uio.default.ums.integration.password |
Password for Oracle User Messaging Service server |
|
bharosa.uio.default.ums.integtaion.policies |
Oracle User Messaging Service authentication policies |
|
bharosa.uio.default.ums.integration.fromAddress |
demo@oracle.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 |
|
bharosa.uio.default.ums.integration.deliveryPage.delay |
3000 |
|
bharosa.uio.default.otp.optOut.enabled |
false |
|
bharosa.uio.default.otp.optOut.managerClass |
com.bharosa.uio.manager.user.DefaultContactInfoManager |
|
bharosa.uio.default.userinfo.inputs.enum.terms |
4 |
Terms and Conditions enum value |
bharosa.uio.default.userinfo.inputs.enum.terms.name |
Terms and Conditions |
Name for Terms and Conditions checkbox |
bharosa.uio.default.userinfo.inputs.enum.terms.description |
Terms and Conditions |
Description for Terms and Conditions checkbox |
bharosa.uio.default.userinfo.inputs.enum.terms.inputname |
terms |
HTML input name for Terms and Conditions checkbox |
bharosa.uio.default.userinfo.inputs.enum.terms.inputtype |
checkbox |
HTML input type for Terms and Conditions checkbox |
bharosa.uio.default.userinfo.inputs.enum.terms.values |
true |
Required values for Term and Conditions checkbox during registration and user preferences |
bharosa.uio.default.userinfo.inputs.enum.terms.maxlength |
40 |
HTML input max length for Terms and Conditions checkbox |
bharosa.uio.default.userinfo.inputs.enum.terms.required |
true |
Required flag for Term and Conditions checkbox during registration and user preferences |
bharosa.uio.default.userinfo.inputs.enum.terms.order |
5 |
Order on the page for Terms and Conditions checkbox |
bharosa.uio.default.userinfo.inputs.enum.terms.enabled |
true |
Enabled flag for Terms and Conditions enum item |
bharosa.uio.default.userinfo.inputs.enum.terms.regex |
.+ |
Regular expression for validation of Terms and Conditions checkbox |
bharosa.uio.default.userinfo.inputs.enum.terms.errorCode |
otp.invalid.terms |
Error code to get error message from if validation of Terms and Conditions fails |
bharosa.uio.default.userinfo.inputs.enum.terms.managerClass |
com.bharosa.uio.manager.user.DefaultContactInfoManager |
Java class to use to save / retrieve Terms and Conditions from data storage |
bharosa.uio.default.userinfo.inputs.enum.terms.name |
I agree to the [ENTER COMPANY OR SERVICE NAME HERE] terms & conditions. Click to view full <a href="javascript:infoWindow('terms');">Terms & Conditions</a> and <a href="javascript:infoWindow('privacy');">Privacy Policy</a>. |
|
bharosa.uio.default.userinfo.inputs.enum.terms.description |
Message and Data Rates May Apply. <br/>For help or information on this program send "HELP" to [ENTER SHORT/LONG CODE HERE]. <br/>To cancel your plan, send "STOP" to [ENTER SHORT/LONG CODE HERE] at anytime.<br/><br/>For additional information on this service please go to <a href="" target="_blank">[ENTER INFORMATIONAL URL HERE]</a>.<br/><br/><b>Supported Carriers:</b><br/>AT&T, Sprint, Nextel, Boost, Verizon Wireless, U.S. Cellular®, T-Mobile®, Cellular One Dobson, Cincinnati Bell, Alltel, Virgin Mobile USA, Cellular South, Unicel, Centennial and Ntelos |
|
bharosa.uio.default.messages.enum.terms.name |
Terms and Conditions |
|
bharosa.uio.default.messages.enum.terms.description |
PLACEHOLDER TEXT FOR TERMS AND CONDITIONS |
|
bharosa.uio.default.messages.enum.privacy.name |
Privacy Policy |
|
bharosa.uio.default.messages.enum.privacy.description |
PLACEHOLDER TEXT FOR PRIVACY POLICY |
|
bharosa.uio.default.register.userinfo.title |
OTP Anywhere Registration |
|
bharosa.uio.default.register.userinfo.message |
For your protection please enter your mobile telephone number so we may use it to verify your identity in the future. Please ensure that you have text messaging enabled on your phone. |
|
bharosa.uio.default.register.userinfo.registerdevice.message |
Check to register the device that you are currently using as a safe device: |
|
bharosa.uio.default.register.userinfo.continue.button |
Continue |
|
bharosa.uio.default.register.userinfo.decline.message |
If you decline you will not be asked to register again. |
|
bharosa.uio.default.register.userinfo.decline.button |
Decline |
|
bharosa.uio.default.ChallengeSMS.message |
For your protection please enter the code we just sent to your mobile telephone. If you did not receive a code please ensure that text messaging is enabled on your phone and click the resend link below. |
|
bharosa.uio.default.ChallengeSMS.registerdevice.message |
Check to register the device that you are currently using as a safe device: |
|
bharosa.uio.default.ChallengeSMS.continue.button |
Continue |
|
bharosa.uio.default.ChallengeSMS.incorrect.message |
Incorrect OTP. Please try again. |
|
bharosa.uio.default.ChallengeSMS.message.subject |
Oracle OTP Code |
|
bharosa.uio.default.ChallengeSMS.message.body |
Your Oracle SMS OTP Code is: {0} |
|
bharosa.uio.default.userinfo.inputs.enum.mobile |
0 |
Mobile phone enum value |
bharosa.uio.default.userinfo.inputs.enum.mobile.name |
Mobile Phone |
Name for mobile phone field |
bharosa.uio.default.userinfo.inputs.enum.mobile.description |
Mobile Phone |
Description for mobile phone field |
bharosa.uio.default.userinfo.inputs.enum.mobile.inputname |
cell number |
HTML input name for mobile phone field |
bharosa.uio.default.userinfo.inputs.enum.mobile.inputtype |
text |
HTML input type for mobile phone field |
bharosa.uio.default.userinfo.inputs.enum.mobile.maxlength |
15 |
HTML input max length for mobile phone field |
bharosa.uio.default.userinfo.inputs.enum.mobile.required |
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 |
bharosa.uio.default.userinfo.inputs.enum.mobile.enabled |
true |
Enabled flag for mobile phone enum item |
bharosa.uio.default.userinfo.inputs.enum.mobile.regex |
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 |
bharosa.uio.default.userinfo.inputs.enum.mobile.errorCode |
otp.invalid.mobile |
Error code to get 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 |
bharosa.uio.default.userinfo.inputs.enum.mobile2 |
2 |
Mobile phone enum value |
bharosa.uio.default.userinfo.inputs.enum.mobile2.name |
Mobile Phone 2 |
Name for mobile phone field |
bharosa.uio.default.userinfo.inputs.enum.mobile2.description |
Mobile Phone 2 |
Description for mobile phone field |
bharosa.uio.default.userinfo.inputs.enum.mobile2.inputname |
cell number 2 |
HTML input name for mobile phone field |
bharosa.uio.default.userinfo.inputs.enum.mobile2.inputtype |
text |
HTML input type for mobile phone field |
bharosa.uio.default.userinfo.inputs.enum.mobile2.maxlength |
15 |
HTML input max length for mobile phone field |
bharosa.uio.default.userinfo.inputs.enum.mobile2.required |
true |
Required flag for mobile phone field during registration and user preferences |
bharosa.uio.default.userinfo.inputs.enum.mobile2.order |
2 |
Order on the page for mobile phone field |
bharosa.uio.default.userinfo.inputs.enum.mobile2.enabled |
true |
Enabled flag for mobile phone enum item |
bharosa.uio.default.userinfo.inputs.enum.mobile2.regex |
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 |
bharosa.uio.default.userinfo.inputs.enum.mobile2.errorCode |
otp.invalid.mobile |
Error code to get 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 |
bharosa.uio.default.challenge.type.enum.ChallengeSMS |
2 |
SMS Challenge enum value |
bharosa.uio.default.challenge.type.enum.ChallengeSMS.name |
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.SMSUMSOTPChallengeProcessor |
Processor class for SMS challenge type Specifies the java class for handling challenges of this type. The challenge mechanism is customizable through Java classes. |
bharosa.uio.default.challenge.type.enum.ChallengeSMS.requiredInfo |
mobile,terms |
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.displayedInfo |
mobile |
|
bharosa.uio.default.challenge.type.enum.ChallengeSMS.available |
false |
Availability flag for 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. |
bharosa.uio.default.challenge.type.enum.ChallengeSMS.otp |
true |
OTP flag for SMS challenge type |
bharosa.uio.default.challenge.type.enum.ChallengeSMS.otpexpirytimeMs |
300000 |
Sets up OTP SMS password expiry time. The time is in milliseconds. If the value is not in milliseconds, you will have to perform a conversion. For example, if you want to set the expiration time for OTP to be 7 minutes, then you must set the property to 420000 (7 minutes) |
bharosa.uio.default.challenge.type.enum.ChallengeSMS.htmlLabel |
SMS Code |
Label used when HTML (not authentipad) is used for user input. Resource bundle value. |
bharosa.uio.default.challenge.type.enum.ChallengeSMS.htmlInputType |
text |
Type of input used when HTML (not authentipad) is used for user input. Possible values are "text" or "password". |
bharosa.uio.default.userinfo.inputs.enum.email |
1 |
Email address enum value |
bharosa.uio.default.userinfo.inputs.enum.email.name |
Email Address |
Name for email address field |
bharosa.uio.default.userinfo.inputs.enum.email.description |
Email Address |
Description for email address field |
bharosa.uio.default.userinfo.inputs.enum.email.inputname |
|
HTML input name for email address field |
bharosa.uio.default.userinfo.inputs.enum.email.inputtype |
text |
HTML input type for email address field |
bharosa.uio.default.userinfo.inputs.enum.email.maxlength |
40 |
HTML input max length for email address field |
bharosa.uio.default.userinfo.inputs.enum.email.required |
true |
Required flag for email address field during registration and user preferences |
bharosa.uio.default.userinfo.inputs.enum.email.order |
2 |
Order on the page for email address field |
bharosa.uio.default.userinfo.inputs.enum.email.enabled |
false |
Enabled flag for email address enum item |
bharosa.uio.default.userinfo.inputs.enum.email.regex |
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} |
Regular expression for validation of email address field |
bharosa.uio.default.userinfo.inputs.enum.email.errorCode |
otp.invalid.email |
Error code to get error message from if validation of email address entry fails |
bharosa.uio.default.userinfo.inputs.enum.email.managerClass |
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 |
bharosa.uio.default.userinfo.inputs.enum.email2.name |
Email Address 2 |
Name for email address field |
bharosa.uio.default.userinfo.inputs.enum.email2.description |
Email Address 2 |
Description for email address field |
bharosa.uio.default.userinfo.inputs.enum.email2.inputname |
email2 |
HTML input name for email address field |
bharosa.uio.default.userinfo.inputs.enum.email2.inputtype |
text |
HTML input type for email address field |
bharosa.uio.default.userinfo.inputs.enum.email2.maxlength |
40 |
HTML input max length for email address field |
bharosa.uio.default.userinfo.inputs.enum.email2.required |
true |
Required flag for email address field during registration and user preferences |
bharosa.uio.default.userinfo.inputs.enum.email2.order |
2 |
Order on the page for email address field |
bharosa.uio.default.userinfo.inputs.enum.email2.enabled |
false |
Enabled flag for email address enum item |
bharosa.uio.default.userinfo.inputs.enum.email2.regex |
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} |
Regular expression for validation of email address field |
bharosa.uio.default.userinfo.inputs.enum.email2.errorCode |
otp.invalid.email |
Error code to get 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 |
bharosa.uio.default.userinfo.inputs.enum.phone |
2 |
Phone number enum value |
bharosa.uio.default.userinfo.inputs.enum.phone.name |
Phone Number |
Name for phone number field |
bharosa.uio.default.userinfo.inputs.enum.phone.description |
Phone Number |
Description for phone number field |
bharosa.uio.default.userinfo.inputs.enum.phone.inputname |
phone |
HTML input name for phone number field |
bharosa.uio.default.userinfo.inputs.enum.phone.inputtype |
text |
HTML input type for phone number field |
bharosa.uio.default.userinfo.inputs.enum.phone.maxlength |
15 |
HTML input max length for phone number field |
bharosa.uio.default.userinfo.inputs.enum.phone.required |
true |
Required flag for phone number field during registration and user preferences |
bharosa.uio.default.userinfo.inputs.enum.phone.order |
3 |
Order on the page for phone number field |
bharosa.uio.default.userinfo.inputs.enum.phone.enabled |
false |
Enabled flag for phone number enum item |
bharosa.uio.default.userinfo.inputs.enum.phone.regex |
\\D?(\\d{3})\\D?\\D?(\\d{3})\\D?(\\d{4}) |
Regular expression for validation of phone number field |
bharosa.uio.default.userinfo.inputs.enum.phone.errorCode |
otp.invalid.phone |
Error code to get error message from if validation of phone number entry fails |
bharosa.uio.default.userinfo.inputs.enum.phone.managerClass |
com.bharosa.uio.manager.user.DefaultContactInfoManager |
Java class to use to save / retrieve phone number from data storage |
bharosa.uio.default.userinfo.inputs.enum.im |
3 |
Instant message enum value |
bharosa.uio.default.userinfo.inputs.enum.im.name |
Instant Messaging |
Name for instant message field |
bharosa.uio.default.userinfo.inputs.enum.im.description |
Instant Messaging |
Description for instant message field |
bharosa.uio.default.userinfo.inputs.enum.im.inputname |
im |
HTML input name for instant message field |
bharosa.uio.default.userinfo.inputs.enum.im.inputtype |
text |
HTML input type for instant message field |
bharosa.uio.default.userinfo.inputs.enum.im.maxlength |
15 |
HTML input max length for instant message field |
bharosa.uio.default.userinfo.inputs.enum.im.required |
true |
Required flag for instant message field during registration and user preferences |
bharosa.uio.default.userinfo.inputs.enum.im.order |
4 |
Order on the page for instant message field |
bharosa.uio.default.userinfo.inputs.enum.im.enabled |
false |
Enabled flag for instant message enum item |
bharosa.uio.default.userinfo.inputs.enum.im.regex |
Regular expression for validation of instant message field |
|
bharosa.uio.default.userinfo.inputs.enum.im.errorCode |
otp.invalid.im |
Error code to get error message from if validation of instant message entry fails |
bharosa.uio.default.userinfo.inputs.enum.im.managerClass |
com.bharosa.uio.manager.user.DefaultContactInfoManager |
Java class to use to save / retrieve instant message from data storage |
bharosa.uio.default.ChallengeEmail.message.from.name |
Oracle ASA Test |
Email message from address |
bharosa.uio.default.ChallengeEmail.message.subject |
Oracle OTP Code |
Email message subject |
bharosa.uio.default.ChallengeEmail.message.body |
Your Oracle Email OTP Code is: {0} |
Email message body |
bharosa.uio.default.ChallengeIM.message.from.name |
Oracle ASA Test |
IM message from name |
bharosa.uio.default.ChallengeIM.message.subject |
Oracle OTP Code |
IM message subject |
bharosa.uio.default.ChallengeIM.message.body |
Your Oracle IM OTP Code is: {0} |
IM message body |
bharosa.uio.default.challenge.type.enum.ChallengeEmail |
1 |
Email Challenge enum value |
bharosa.uio.default.challenge.type.enum.ChallengeEmail.name |
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.EmailUMSOTPChallengeProcessor |
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. |
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.displayedInfo |
|
|
bharosa.uio.default.challenge.type.enum.ChallengeEmail.available |
false |
Availability flag for 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. |
bharosa.uio.default.challenge.type.enum.ChallengeEmail.enabled |
true |
|
bharosa.uio.default.challenge.type.enum.ChallengeEmail.otp |
true |
OTP flag for e-mail challenge type |
bharosa.uio.default.challenge.type.enum.ChallengeEmail.otpexpirytimeMs |
300000 |
Sets up OTP Email password expiry time. The time is in milliseconds. If the value is not in milliseconds, you will have to perform a conversion. For example, if you want to set the expiration time for OTP to be 7 minutes, then you must set the property to 420000 (7 minutes) |
bharosa.uio.default.challenge.type.enum.ChallengeEmail.htmlLabel |
Email Code |
Label used when HTML (not authentipad) is used for user input. Resource bundle value. |
bharosa.uio.default.challenge.type.enum.ChallengeEmail.htmlInputType |
text |
Type of input used when HTML (not authentipad) is used for user input. Possible values are "text" or "password". |
bharosa.uio.default.challenge.type.enum.ChallengeIM |
3 |
Instant message Challenge enum value |
bharosa.uio.default.challenge.type.enum.ChallengeIM.name |
IM Challenge |
Name of instant message challenge type |
bharosa.uio.default.challenge.type.enum.ChallengeIM.description |
Instant Message Challenge |
Description of instant message challenge type |
bharosa.uio.default.challenge.type.enum.ChallengeIM.processor |
com.bharosa.uio.processor.challenge.ChallengeIMProcessor |
Processor class for instant message challenge type |
bharosa.uio.default.challenge.type.enum.ChallengeIM.requiredInfo |
mobile |
Required fields to challenge user with instant message challenge type |
bharosa.uio.default.challenge.type.enum.ChallengeIM.available |
false |
Availability flag for instant message challenge type |
bharosa.uio.default.challenge.type.enum.ChallengeIM.otp |
true |
OTP flag for instant message challenge type |
bharosa.uio.default.ChallengeChoice.title |
Title for Challenge Choice page. |
|
bharosa.uio.default.ChallengeChoice.message |
Select how you would prefer to receive OTP code. |
|
bharosa.uio.default.ChallengeChoice.continue.message |
Continue message. |
|
bharosa.uio.default.ChallengeChoice.continue.button |
Continue |
|
bharosa.uio.default.ChallengeChoice.invalid_choice.message |
You have entered an invalid choice. Please check your selection and try again. |
|
bharosa.uio.default.ChallengeChoice.not_available.message |
Selected challenge type is not available. Please select again. |
|
bharosa.uio.default.ChallengeChoice.continue.enabled |
true |
|
bharosa.uio.default.ChallengeQuestion.links.enum.choice |
4 |
|
bharosa.uio.default.ChallengeQuestion.links.enum.choice.name |
Change choice |
|
bharosa.uio.default.ChallengeQuestion.links.enum.choice.description |
Choose different challenge method. |
|
bharosa.uio.default.ChallengeQuestion.links.enum.choice.url |
javascript:newChoice(); |
|
bharosa.uio.default.ChallengeQuestion.links.enum.choice.personalization |
false |
|
bharosa.uio.default.ChallengeQuestion.links.enum.choice.challengechoice |
true |
|
bharosa.uio.default.ChallengeQuestion.links.enum.choice.order |
4 |
|
bharosa.uio.default.ChallengeQuestion.links.enum.choice.enabled |
true |
|
bharosa.uio.default.ChallengeEmail.links.enum.choice |
4 |
|
bharosa.uio.default.ChallengeEmail.links.enum.choice.name |
Change choice |
|
bharosa.uio.default.ChallengeEmail.links.enum.choice.description |
Choose different delivery method. |
|
bharosa.uio.default.ChallengeEmail.links.enum.choice.url |
javascript:newChoice(); |
|
bharosa.uio.default.ChallengeEmail.links.enum.choice.personalization |
false |
|
bharosa.uio.default.ChallengeEmail.links.enum.choice.challengechoice |
true |
|
bharosa.uio.default.ChallengeEmail.links.enum.choice.order |
4 |
|
bharosa.uio.default.ChallengeEmail.links.enum.choice.enabled |
true |
|
bharosa.uio.default.ChallengeSMS.links.enum.choice |
4 |
|
bharosa.uio.default.ChallengeSMS.links.enum.choice.name |
Change choice |
|
bharosa.uio.default.ChallengeSMS.links.enum.choice.description |
Choose different delivery method. |
|
bharosa.uio.default.ChallengeSMS.links.enum.choice.url |
javascript:newChoice(); |
|
bharosa.uio.default.ChallengeSMS.links.enum.choice.personalization |
false |
|
bharosa.uio.default.ChallengeSMS.links.enum.choice.challengechoice |
true |
|
bharosa.uio.default.ChallengeSMS.links.enum.choice.order |
4 |
|
bharosa.uio.default.ChallengeSMS.links.enum.choice.enabled |
true |
|
bharosa.uio.default.ChallengeIM.links.enum.choice |
4 |
|
bharosa.uio.default.ChallengeIM.links.enum.choice.name |
Change choice |
|
bharosa.uio.default.ChallengeIM.links.enum.choice.description |
Choose different delivery method. |
|
bharosa.uio.default.ChallengeIM.links.enum.choice.url |
javascript:newChoice(); |
|
bharosa.uio.default.ChallengeIM.links.enum.choice.personalization |
false |
|
bharosa.uio.default.ChallengeIM.links.enum.choice.challengechoice |
true |
|
bharosa.uio.default.ChallengeIM.links.enum.choice.order |
4 |
|
bharosa.uio.default.ChallengeIM.links.enum.choice.enabled |
true |
|
bharosa.uio.default.ChallengeVoice.links.enum.choice |
4 |
|
bharosa.uio.default.ChallengeVoice.links.enum.choice.name |
Change choice |
|
bharosa.uio.default.ChallengeVoice.links.enum.choice.description |
Choose different delivery method. |
|
bharosa.uio.default.ChallengeVoice.links.enum.choice.url |
javascript:newChoice(); |
|
bharosa.uio.default.ChallengeVoice.links.enum.choice.personalization |
false |
|
bharosa.uio.default.ChallengeVoice.links.enum.choice.challengechoice |
true |
|
bharosa.uio.default.ChallengeVoice.links.enum.choice.order |
4 |
|
bharosa.uio.default.ChallengeVoice.links.enum.choice.enabled |
true |
|
bharosa.uio.default.ChallengeChoice.title |
Title for Challenge Choice page. |
|
bharosa.uio.default.ChallengeChoice.message |
Select how you would prefer to receive OTP code. |
|
bharosa.uio.default.ChallengeChoice.continue.message |
Continue message. |
|
bharosa.uio.default.ChallengeChoice.continue.button |
Continue |
|
bharosa.uio.default.ChallengeChoice.invalid_choice.message |
You have entered an invalid choice. Please check your selection and try again. |
|
bharosa.uio.default.ChallengeChoice.not_available.message |
Selected challenge type is not available. Please select again. |
|
bharosa.uio.default.challenge.type.enum.ChallengeQuestion.displayedInfo |
||
bharosa.uio.default.challenge.type.enum.ChallengeEmail.displayedInfo |
|
|
bharosa.uio.default.challenge.type.enum.ChallengeSMS.displayedInfo |
mobile |
|
bharosa.uio.default.challenge.type.enum.ChallengeIM.displayedInfo |
im |
|
bharosa.uio.default.challenge.type.enum.ChallengeVoice.displayedInf |
phone |
|
bharosa.uio.default.otp.generate.code.length |
5 |
Designates the length of the OTP. |
bharosa.uio.default.otp.generate.code.characters |
1234567890 |
Designates the characters to use when generating the OTP. |
bharosa.uio.default.challenge.type.enum.ChallengeSMS.otpexpirytimeMs |
mobile |
OTP SMS password expiry time in milliseconds. |
bharosa.uio.default.ChallengeChoice.actionlist.threshold |
3 |
Minimum number of actions in action list to trigger challenge choice. |
bharosa.uio.default.ChallengeChoice.contactInfo.delim |
- |
Sets the delimiter for contact information displayed in the Challenge Choice page. |
bharosa.uio.default.ChallengeChoice.contactInfo.mask |
* |
Sets the replacement character for masking for contact information displayed in the Challenge Choice page. |
Table C-23 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 |
vcrypt.tracker.rulelog.detailed.minMillis |
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-24 Policies, Rules, and Condition Properties
Properties | Description |
---|---|
vcrypt.tracker.rules.trace.policySet.XXXXXX |
Specifies the checkpoint in which to log the rules. Make sure that "vcrypt.tracker.rules.trace.policySet.XXXXXX" is set to |
vcrypt.tracker.rules.allowControlledActions |
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 Enterprise Deployment Guide for Oracle Identity and Access Management. |
bharosa.uio.proxy.mode.flag |
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-27 SOAP Web Service Access Properties
Property | Description |
---|---|
vcrypt.soap.auth |
Disables or enables HTTP authentication for Authenticator. set the following property to true (enabled) or false (disabled). |
vcrypt.tracker.soap.url |
SOAP Server Side URL. This setting is the location of the web services with which the application will communicate. |
vcrypt.common.util.vcryptsoap.impl.classname |
Specifies for the application which libraries to use when creating SOAP messages to exchange with the OAAM services. The available option is com.bharosa.vcrypt.common.impl.VCryptSOAPGenericImpl |
vcrypt.soap.call.timeout |
SOAP call timeout in milliseconds |
keystorepasswd |
Password for opening the keystore. |
keystorealiaspasswd |
Password reading alias (key) in the keystore |
keyFile= |
File containing from key. Please note, keys in AES could be binary. Also note algorithms like 3DES require minimum 24 characters in the key. For example, keyFile=soap_key.file. |
keystorefilename |
keystorefilename=system_soap.keystore Keystore file name. |
keystorealias |
keystorealias=vcrypt.soap.call.passwd Keystore alias. |
vcrypt.soap.auth.keystorePassword=<base64 encoded keystore password> vcrypt.soap.auth.aliasPassword=<based64 encoded password to the alias> vcrypt.soap.auth.username=<user configured for accessing the soap services> vcrypt.soap.auth.keystoreFile=system_soap.keystore |
Properties with the encoded passwords and the authentication user name to add to |
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 |
---|---|
vcrypt.user.account.status.enum.pending_activation.name |
Pending Activation The user started registration, but has not completed it. He has entered his user name 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. |
vcrypt.user.account.status.enum.active.name |
Active The user is active and available in the system. He has completed registration and can perform all operations. |
vcrypt.user.account.status.enum.disabled.name |
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. |
vcrypt.user.account.status.enum.deleted.name |
Deleted The user is not available in the system. |
vcrypt.user.account.status.enum.invalid.name |
Invalid The user name 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-29 Authentication Status
Properties | Description |
---|---|
auth.status.enum.success.name |
Success The user is successfully authenticated. |
auth.status.enum.invalid_user.name |
Invalid user The user name was invalid and not available in the system. |
auth.status.enum.wrong_password.name |
Wrong password The user entered the wrong password. The user name was entered correctly, but the password was incorrect. |
auth.status.enum.wrong_pin.name |
Wrong PIN If user has PIN as a password and it was entered incorrectly. |
auth.status.enum.session_expired.name |
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. |
auth.status.enum.session_reused.name |
Session reused When the session had expired and the user logged in successfully, the status changes from session expired to session reused. |
auth.status.enum.user_disabled.name |
User disabled The user was available in the system, but had been disabled in the system for a variety of reasons. The user name is valid, but he has been disabled. |
auth.status.enum.pending_activation.name |
Pending activation The user has not completed the registration yet. |
auth.status.enum.wrong_answer.name |
Wrong Answer The user entered the wrong answer to a challenge question. |
auth.status.enum.db_error.name |
Database Error When user was performing a database operation, he encountered an error. |
auth.status.enum.system_error.name |
System Error When user was using the application, he encountered an error. |
auth.status.enum.block.name |
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." |
auth.status.enum.challenge_block.name |
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 user can use the account to enter the system. |
auth.status.enum.pending.name |
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-30 Timezones Properties
Properties | Description |
---|---|
oaam.adf.timezone |
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) |
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) |
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) |
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) |
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-31 User Interface Properties
Properties | Description |
---|---|
bharosa.uio.default.username.case.sensitive |
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. |
oaam.export.max.rows.allowed |
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. |
fa.default.daterange.in.hours |
Search screen default time range. |
oaam.session.filter.timerange.enum.oneday.typevalue |
Session screen default time range. |
oaam.alerts.max.rows.display |
Limits the number of alerts to display in the Transaction and Alert pop-ups for viewing alert messages through the "..." or "more..." option in the Linked Sessions tab of the Agent case and the Search Sessions screens. The other screens that show alerts are the Session tab for the Detail screens (User, Device, Fingerprint, IP, Country, State, City), Transaction Search, and Session Details pages. The maximum limit is currently set to five alerts in the pop-up. |
oracle.oaam.db.query.maxrows |
Allows you to set a limit to the number of result rows. The default value for this parameter is 0. This value should never be set to be smaller than 100 or smaller than the number of members in your largest group with a full cache policy. |
Table C-32 Virtual Authentication Device Properties
Properties | Description |
---|---|
bharosa.user.noun.list bharosa.user.adj.list |
Customize the phrase in the virtual authentication device by setting the following two parameters. The authenticator phrase is created by these two properties. Both are comma-delimited lists of words. Examples: actors,age,air,aircraft abundant,accessible,accommodating |
vcrypt.user.image.dirlist.property.name=bharosa.image.dirlist bharosa.image.dirlist= |
Set the properties for images to be displayed. bharosa.image.dirlist sets is the location of the image files that the application will use when creating authentication images. The directory contains 1000 images. bharosa.image.dirlist=/bharosa_images/allpads/textpad/ vcrypt.user.image.dirlist.property.name=bharosa.image.dirlist |
bharosa.authentipad.questionpad.datafield.input.type |
The property in Valid values are text and password. |
bharosa.authentipad.image.url |
bharosa.authentipad.image.url=kbimage.jspaction=kbimage& Specifies the URL file and query parameters to use when displaying an image for challenge. |
bharosa.uio.default.DeviceTextPad.default.image |
default background property textpad_bg/TP_NCC_bg.jpg |
bharosa.authentipad.textpad.datafield.maxLength |
25 Controls the number of bytes the TextPad accepts for a password. |
vcrypt.caption.assignDefault |
Instructs the server not to assign a caption to the user's registration image if set to false. |
desertref.authentipad.isADACompliant |
Enables accessible versions of the virtual authentication devices in native integration if this ADA compliant property is set to true. The accessible versions of the pads contain tabbing, directions and ALT text necessary for navigation via screen reader and other assistive technologies. |
bharosa.uio.default.authentipad.is_ada_compliant |
Enables accessible versions of the virtual authentication devices in UIO if this ADA compliant property is set to true. The accessible versions of the pads contain tabbing, directions and ALT text necessary for navigation via screen reader and other assistive technologies. |
bharosa.uio.default.signon.links.enum.wherepassword.enabled |
Enables/disables single login page. |