A masking algorithm must be created for each security type.
These algorithms determine if a user has the rights to view a given
field unmasked, and, if not, how the field should be masked.
The base package provides the algorithm type
F1-MASK whose parameters are designed to handle most masking
needs. This algorithm type's parameters are described below to provide
the complete picture of how to control how a field is masked and who
can see it unmasked:
-
Masking Character: Enter the character
used to overwrite a field's value for users who can only see masked
values.
-
Number of Unmasked Characters: If some
of the field value should remain unmasked at the end of the string,
enter the number of unmasked characters.
-
Unmasked Characters: If some characters
in a field value should never be masked, enter them. For example,
if a phone number can contain dashes and parenthesis and you don't
want these characters masked, you would enter -()..
-
Application Service: Enter the application
service that you created above.
-
Security Type: Enter the security type
that you created above.
-
Authorization Level: Enter the authorization
level that a user must have to see this field unmasked. If you followed
the recommendations above, this will be 2.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.