The IdentityMappingRuleType structure defines a single rule for selecting a UserIdentityToken. The structure is described in Table 7.
Table 7 – IdentityMappingRuleType
|IdentityMappingRuleType||Structure||Specifies a rule used to map a UserIdentityToken to a Role.|
|criteriaType||EnumerationIdentityCriteriaType||The type of criteria contained in the identity mapping rule. The IdentityCriteriaType is defined in 4.4.4.|
|criteria||String||The criteria which the UserIdentityToken must meet for a Session to be mapped to the Role. The meaning of the criteria depends on the criteriaType. The criteria are a “” for Anonymous and AuthenticatedUser.|
If the criteriaType is UserName, the criteria is a name of a user known to the Server, For example, the user could be the name of a local operating system account or a user managed by the server as defined in 5.2.
If the criteriaType is Thumbprint, the criteria is a thumbprint of an immediate user Certificate or an issuer Certificate in its chain which is trusted by the Server. For the criteria, the thumbprint shall be encoded as a hexadecimal string with upper case characters and without spaces.
If the criteriaType is Role, the criteria is a name of a restriction found in the Access Token. For example, the Role “subscriber” may only be allowed to access PubSub related Nodes.
If the criteriaType is GroupId, the criteria is a generic text identifier for a user group specific to the Authorization Service. For example, an Authorization Service providing access to an Active Directory may add one or more Windows Security Groups to the Access Token. OPC 10000-6 provides details on how groups are added to Access Tokens.
If the criteriaType is Anonymous, the criteria is a null string which indicates no user credentials have been provided.
If the criteriaType is AuthenticatedUser, the criteria is a null string which indicates any valid user credentials have been provided.
If the criteriaType is Application, the criteria is the ApplicationUri from the Client Certificate used for the Session. The Client Certificate shall be trusted by the Server and the Session shall use at least a signed communication channel. This criteria type is used if a Role should be granted to a Session for Application Authentication with Anonymous UserIdentityToken. If a Role should be granted to a Session for Application Authentication combined with User Authentication, the Applications Property on the RoleType is combined with the Identities Property on the RoleType as defined in 4.4.1.
If the criteriaType is X509Subject, the criteria is the X509 subject name of a Certificate of a user which is trusted by the Server. The format of the subject name criteria consists of a sequence of name value pairs separated by a ‘/’. The name shall be one of entries in Table 8 and shall be followed by a ‘=’ and then followed by the value, which is always enclosed in double quotes (‘”’). The order shall be by the order shown in Table 8 with the lowest number first. Every value from Table 8 present in the Certificate shall be included in the criteria, others must not be included. The value may be any printable character except for ‘”’. For example: CN=”User Name”/O=”Company”. Table 8 contains all subject name attributes where support is required by X509 and some commonly used attributes where support is optional. Additional fields may be added in the future. If one name is used multiple times in the certificate, the name is also repeated in the criteria. The entries with the same name are entered in the order they appear in the Certificate. All names listed in Table 8 that are included in the X509 subject name shall match the content of the criteria String. Names not included in Table 8 are ignored.
Table 8 – Order for subject name criteria
|8||dnQualifier||Distinguished name qualifier|
The IdentityMappingRuleType Structure representation in the AddressSpace is defined in Table 9.
Table 9 – IdentityMappingRuleType definition
|Subtype of Structure defined in OPC 10000-5.|
|Base Info ServerType|