previous

Viewing Masked Fields in OPERA

The encryption or masking of sensitive customer information appears by default on many of the ID type fields and birth date fields throughout OPMS and ORS.

In ORS, the Profile ID Numbers and Birth_Date Encryption process encrypts the Birth_Date and ID Types that are stored in the database for profiles.

When your user is granted the PROFILES > VIEW SENSITIVE INFORMATION ON PROFILE permission, you can unmask these encrypted fields on certain screens and view this information.

Scenario 1: User is granted VIEW SENSITIVE INFORMATION ON PROFILE

Screens Affected by Permission

ORS Merge

When the VIEW SENSITIVE INFORMATION ON PROFILE permission is granted, all encrypted fields can be unmasked.

By default, the BIRTH_DATE and ID Types are masked on the ORS Merge screen.

Unmasking Fields

Encrypted fields can be unmasked by selecting the Unmask button. The fields remain unmasked when moving from the Suspended Profile Matches screen to the Three-Panel Merge screen. The fields also remain unmasked when you view other profiles on the screen.

When you unmask fields, the User Activity Log records the fields that are unmasked by your user.

Profile Screen

By default, the BIRTH_DATE and ID Types are masked for all profiles.

When the VIEW SENSITIVE INFORMATION ON PROFILE permission is granted, all encrypted fields can be unmasked.

Unmasking Fields

In ORS and OPMS, fields can be unmasked by Shift + Ctrl + Double Click.

When you unmask fields, the User Activity Log records the fields that are unmasked by your user.

Other Areas

OPERA Scheduler

When the OPERA Scheduler runs, existing ID Types and BIRTH_DATE fields are encrypted in the database. The VIEW SENSITIVE INFORMATION ON PROFILE permission must be granted to unmask and view this information.

Reports

By default, all reports, registration cards, data extractions and exports have ID Types and BIRTH_DATE fields masked.

When the VIEW SENSITIVE INFORMATION ON PROFILE permission is granted, you have the option to generate reports, registration cards, data extractions and exports with ID Types and BIRTH_DATE fields unmasked. The User Activity Log records the fields that are unmasked by your user.

OXI/OXI-HUB

BIRTH_DATE and ID Types are always encrypted in the XML messages.

Database

Birth_Date is encrypted in the name table.

Passport and ID Types are encrypted in the name_documents table.

Scenario 2: User is not granted VIEW SENSITIVE INFORMATION ON PROFILE

ID Type and BIRTH_DATE fields cannot be unmasked on any of the above mentioned screens or in any of the above mentioned areas.