The suggested values setting allows you to configure predefined values from which you can choose when using the claim type in a conditional expression. If you create a claim type without suggested values, you will have to type rather than select values in the condition builder. Another option is to create one or more suggested values for the claim type. These values will appear in a list provided by the condition builder.
You can add, edit or remove suggested values for a given claim type when creating or modifying the respective claim type object. When you add or edit a suggested value, you are prompted to complete the following fields:
-
Value: This value data will be used when evaluating conditional expressions that include the suggested value you are configuring.
-
Display name: This is the name of the suggested value that appears in the list when you configure a conditional expression.
Claim types must be created in Active Directory to enable domain controllers (DCs) to issue claims to users or computers. Claims issued by the DC are sourced from attributes of user or computer accounts stored in Active Directory. Claim types specify the attributes from which the claims are sourced, and contain metadata required for using claims.
New claim types are created in the Claim Types container under the Active Directory node located in the Active Roles Console tree. If you have domains from multiple forests registered with Active Roles, then the Console displays an individual Claim Types container for each forest that has DCs running Windows Server 2016 or a later version of the Windows Server operating system. To identify the forest of a given Claim Types container, the container name includes the name (or a part of the name) of the forest root domain.
To create a new claim type
-
Right-click the Claim Types container, and select New > Claim Type.
-
On the Source Attribute page, select the desired source attribute for claims of this type.
-
Review the auto-generated display name and description, and change them if needed.
-
Under Claims of this type can be issued for the following classes, select:
-
Select the Set ID to a semantically identical claim type in a trusted forest check box if the claim type must match an existing claim type in a different forest. Type the claim identifier. Clear this check box to generate the claim identifier automatically.
-
Select the Protect from accidental deletion check box to ensure an administrator cannot accidentally delete the claim type. Clear the check box to remove accidental deletion protection.
-
Click Next to proceed to the Suggested Values page.
-
Click the option you want for suggested values. Create suggested values as needed.
-
Click Finish.
To modify an existing claim type
-
Right-click the claim type you want to modify and then click Properties.
-
On the Source Attribute page, view or change the source attribute, the display name, description, user or computer claim issuance options, and the option to protect the claim type from accidental deletion.
-
Click the Suggested Values tab to view or change suggested values.
-
Click OK to save the modified claim type.
To delete a claim type
-
Right-click the claim type and then click Delete.
-
Confirm the claim type deletion.
If you encounter a message stating that you do not have permission to delete the claim type, then modify the claim type and clear the Protect from accidental deletion check box. If this check box is cleared, verify that you have sufficient rights to delete claim type objects.
Windows claim types have two states: disabled and enabled. Disabled claim types are valid claim types, but are unavailable for use in production. Claims of disabled claim types are not issued by domain controllers and disabled claim types are filtered from view in the access rule condition builder. A claim type becomes available for production use once you enable it. Active Roles creates enabled claim types, and allows you to disable and enable claim types as needed.
To disable an enabled claim type
To enable a disabled claim type
Creating a claim type object makes the Active Directory forest aware of the claim type. However, claim type objects do not provide information held in the actual claims. When issuing claims, domain controllers (DCs) retrieve that information from user and computer objects. Hence, in addition to claim type objects, user and computer objects must contain the information necessary for DCs to issue claims.
Attribute-based claim types define the attributes from which to source the claims. These are attributes of user and computer objects. Each claim type object specifies a certain attribute that the DC retrieves when creating and issuing claims of that type. During authentication of a user, the claim-aware DC reads all enabled claim types from the user’s Active Directory forest, and maps them to the attributes of the authenticating user or computer. Then, the DC retrieves information from the mapped attributes, and issues claims containing that information.
As DCs do not issue blank claims, you may encounter a situation where you have created a valid claim type but the DC does not issue the claim during authentication. This is because a claim type object merely maps claims to a certain attribute, directing the DC to issue claims based on the information present in that attribute. If the attribute of the authenticating user or computer does not contain information, the DC does not issue the claim.
Therefore, it is important that claim source attributes contain information. Additionally, as authorization decisions depend upon information found in claims, claim source attributes must contain valid information. Incorrect attribute information can lead to unexpected access to data using claims-based authorization.
To ensure that claim source attributes contain valid information, you could periodically inspect and, if needed, set or correct the properties of users and computers by using the Active Roles Console or Web Interface. However, it would be more practical to leverage property generation and validation policies provided by Active Roles. You can use policies to:
-
Auto-generate the appropriate values for user and computer properties upon creation of user and computer objects.
-
Prevent invalid values from being assigned to user and computer properties, by applying validation rules or creating immutable lists of suggested values.