Challenge Type Enum Define the Delivery Channel Types for the Challenge Processors

21-2 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager

21.2 Schema Examples

The OAAM Schema and custom schema are shown below.

21.2.1 OAAM Schema

The following example shows the SQL for the OAAM_LOAD_DATA_VIEW that ships with OAAM. CREATE OR REPLACE FORCE VIEW OAAM_LOAD_DATA_VIEW LOGIN_TIMESTAMP, SESSION_ID, USER_ID, LOGIN_ID, DEVICE_ID, GROUP_ID, IP_ADDRESS, AUTH_STATUS, CLIENT_TYPE, USER_AGENT, FLASH_FINGERPRINT, DIGITAL_COOKIE, EXP_DIGITAL_COOKIE, SECURE_COOKIE, EXP_SECURE_COOKIE AS SELECT l.create_time LOGIN_TIMESTAMP, l.request_id SESSION_ID, l.user_id USER_ID, l.user_login_id LOGIN_ID, l.node_id DEVICE_ID, l.user_group_id GROUP_ID, l.remote_ip_addr IP_ADDRESS, l.auth_status AUTH_STATUS, l.auth_client_type_code CLIENT_TYPE, SELECT t1.data_value FROM v_fprints t1 WHERE t1.fprint_id=l.fprint_id USER_ AGENT, SELECT t2.data_value FROM v_fprints t2 WHERE t2.fprint_id=l.digital_fp_id FLASH_FINGERPRINT, l.sent_dig_sig_cookie DIGITAL_COOKIE, l.expected_dig_sig_cookie EXP_DIGITAL_ COOKIE, l.sent_secure_cookie SECURE_COOKIE, l.expected_secure_cookie EXP_SECURE_COOKIE FROM vcrypt_tracker_usernode_logs l; For discussion purposes, consider this statement in two parts. The first part starts at the beginning and ends before the Select. This part is required and cannot be modified. The second part starts with the Select and continues to the end of the statement. If loading from a non-OAAM schema, this part would be customized to select data from that schema.

21.2.2 Custom Schema Example

In this example, you would want to load from a table that looks like the following. You would want to have Banking as your primary group or Application ID, and you would not want to load test data. LOGINS EXP_DIGITAL_COOKIE Character This field represents the expected digital cookie set by OAAM. When loading from a non-OAAM schema, this should be null. SECURE_COOKIE Character This field represents the secure cookie set by OAAM. When loading from a non-OAAM schema, this should be null. EXP_SECURE_COOKIE Character This field represents the expected secure cookie set by OAAM. When loading from a non-OAAM schema, this should be null. Table 21–1 Cont. OAAM_LOAD_DATA_VIEW Field Name Data Type Description Creating a View of a Non-OAAM Database 21-3 In this case, a decode statement is needed to convert the custom authentication status to an OAAM authentication status, and the IP address needs to be parsed to convert it into a long integer. A view must be created that looks like the following. CREATE OR REPLACE FORCE VIEW OAAM_LOAD_DATA_VIEW LOGIN_TIMESTAMP, SESSION_ID, USER_ID, LOGIN_ID, DEVICE_ID, GROUP_ID, IP_ADDRESS, AUTH_STATUS, CLIENT_TYPE, USER_AGENT, FLASH_FINGERPRINT, DIGITAL_COOKIE, EXP_DIGITAL_COOKIE, SECURE_COOKIE, EXP_SECURE_COOKIE AS SELECT l.login_time LOGIN_TIMESTAMP, castl.login_id AS varchar2256 SESSION_ID, l.user_name USER_ID, l.user_name, LOGIN_ID, l.device_id DEVICE_ID, Banking GROUP_ID, to_numbersubstrl.ip_address, 1, instrl.ip_address, .-116777216 to_numbersubstrl.ip_address, instrl.ip_address, ., 1, 1+1, instrl.ip_address, ., 1, 2-instrl.ip_address, ., 1, 1-165536 to_numbersubstrl.ip_address, instrl.ip_address, ., 1, 2+1, instrl.ip_address, ., 1, 3-instrl.ip_address, ., 1, 2-1256 to_numbersubstrl.ip_address, instrl.ip_address, ., 1, 3+1 IP_ ADDRESS, decodel.auth_status, S, 0, I, 1, F, 2, -1 AUTH_STATUS, -1 CLIENT_TYPE, l.user_agent USER_AGENT, null FLASH_FINGERPRINT, null DIGITAL_COOKIE, null EXP_DIGITAL_COOKIE, null SECURE_COOKIE, null EXP_SECURE_COOKIE FROM logins l WHERE l.is_test = 0 Here, you map your user_name to USER_ID and LOGIN_ID, you map a literal string Banking to GROUP_ID, you parse your ip_address string and convert it to a long integer, you use a decode statement to convert your auth_status, you map -1 to CLIENT_TYPE, and you map literal null to FLASH_FINGERPRINT, DIGITAL_ COOKIE, EXP_DIGITAL_COOKIE, SECURE_COOKIE, and EXP_SECURE_COOKIE. Table 21–2 LOGINS Field Name Data Type Description LOGIN_TIME DateTime The login time. LOGIN_ID Integer Primary Key USER_NAME Character The users Login ID. DEVICE_ID Character Identifies the users device. IP_ADDRESS Character The IP address, in dot notation. AUTH_STATUS Character S = Success, I = Invalid User, F = Wrong Password. USER_AGENT Character The user agent string from the browser. IS_TEST Integer 0 = Real Data, 1 = Test data