Match Rules - RapidIdentity Platform Documentation

RapidIdentity Platform Documentation
Solution
Application
Content Type
Technical Documentation
Utilities & Services
ft:locale
en-US

Match rules link accounts from source systems to existing identities in RapidIdentity. The following match rule instructs the provisioning system that a source system account is the same identity as a RapidIdentity person when the RapidIdentity idautoPersonStuID value is exactly equal to the source system's sourcedId value:

let key exact idautoPersonStuID = sourcedId

Multiple key groupings (disjunction)

To match using logical OR condition, define multiple key groupings. The following rule matches the source system account to the RapidIdentity person when either condition is true:

let key exact a idautoPersonStuID = id
let key exact b idautoPersonHRID = id
  • The idautoPersonStuID equals the source system id.
  • The idautoPersonHRID equals the source system id.

The key grouping names follow the exact keyword. In this example, the names a and b differ, which produces the disjunction (OR) behavior.

You can also guard the assignments. The following rule matches accounts when either condition is true:

let key exact a idautoPersonStuID = if (roles.contains("student")) id
let key exact b idautoPersonHRID = if (roles.contains("student") == false) id
  • The source user's roles contain student and the id matches idautoPersonStuID.
  • The source user's roles do not contain student and the id matches idautoPersonHRID.

Multiple keys in the same group (conjunction)

To match using a logical AND condition, place more than one match rule in the same key grouping. The following rule matches accounts when both conditions are true:

let key exact a idautoPersonStuID = id
let key exact a mail = email
  • The source user's id is equal to idautoPersonStuID.
  • The source user's email is equal to mail.

A conjunction is useful when id is not guaranteed to be unique in the source system.

Fuzzy keys

In addition to exact keys, you can specify a fuzzy key. A fuzzy key allows a partial match based on Levenshtein distance. The following rule matches accounts when the Levenshtein distance between the three identified source values (first_name, last_name, birthday) puts them within a 75 percent threshold of similarity to a single match of the three identified values (givenName, sn, idautoPersonBirthdate) for a person in RapidIdentity:

let key fuzzy givenName = first_name
let key fuzzy sn = last_name
let key fuzzy idautoPersonBirthdate = birthday
A fuzzy key is a last resort for initial account linking and should only when no other alternatives exist. If a unique match cannot be found, the accounts are not matched.