Add Oracle DB data store

On – Enable membership validation; use the directory to search for the user's membership in a user group.

This means the directory is a Membership Store, containing the password to validate with the username.

After the data store is saved, this field is the Membership Store label shown on the View Summary.

A common use case for a Membership Store would be to have a directory with username and password information (and maybe some profile information), and then have a second directory or database used to store and access data that the Identity Platform writes to the directory (such as device recognition, device enrollment, push notification tokens, and so on).

Off – Disable membership validation; use the directory to search only for the user profile information.

This means the directory is only used to find the username and profile information (such as phone number, email address, device recognition profiles, OATH tokens, and so on).

Username – User name of machine to be scanned by CyberArk Application Identity Manger (AIM). This information appears on the Account Details page of the CyberArk Password Vault Web Access (PVWA) Admin Console

Address – Address of machine to be scanned by AIM

Safe – Name of Access Control Safe where credentials are stored

Folder – Name of folder where account resides (by default, it its the root folder)

Object – Unique identifier Object name for the account

Clear – Password is stored as plain text. This improves performance of storage and retrieval but is less secure.

Encrypted – Password is stored as encrypted and can be decrypted for password comparison or retrieval. This is more secure, but requires additional processing or storage.

Hashed – Password is hashed using a one-way hash algorithm and random salt-value. When password is validated, it is hashed with the salt value of the dates for verification. Hashed passwords cannot be retrieved.