
Now in some cases, you cannot even view those files or folders so this is really frustrating. The sensitive attribute displays as asterisks in the user's profile.However, the thing here is by default, some files or folders saved on Android phone become hidden and you don’t know how.
In the attribute list, click information for the attribute you want to make sensitive. If Profile is unavailable, click User (default). Click Profile for Okta User (default). In the Admin Console, go to Directory > Profile Editor. Only the following Okta base attributes can be marked sensitive: Secondary email, Postal Address, City, and Zip code. See Mapping Active Directory, LDAP, and Workday Values in a Template SAML or WS Fed Applications Using sensitive attributes in SAML assertions provides extra validation when a user is signs in to an app. The data moves from AD, through Okta, to the app.
You then map the Okta user attribute to an app such as Workday. For example, to make an employee number stored in Active Directory (AD) sensitive, you map the AD attribute to the Okta user profile attribute and mark it as sensitive.
To make an attribute sensitive, you map the attribute from the app to the Okta user profile. Changing the setting will not change the field behavior.ĪPI access management - If API access management is enabled for your tenant, these roles can see all attributes in the API token preview functionality in the Admin UI: Super admin, Org admin, Read-only admin, and API AM admin.
The User Permission field - This field is always treated as Hide for sensitive attributes. Users cannot save their profile changes until a Super admin edits the Okta user profile to mark the attribute as not required. The Okta user profile expects the attribute but the user cannot see or edit the attribute. Do not mark a sensitive attribute as required - When a user edits their profile, an error message appears prompting the user to correct Value for required property sensitive is missing. When you make attributes sensitive, consider the following: Okta Super admin permissions are required to make an attribute sensitive and use sensitive attributes in SAML assertions or mapping attributes. Making an Okta user profile attribute sensitive hides information stored in attribute fields.