Home > Storage > PowerScale (Isilon) > Product Documentation > Management and Migration > PowerScale OneFS User Mapping: Mapping Identities Across Authentication Providers > Wildcard matching
A rule can match usernames with a wildcard. If you set the Active Directory domain or the Active Directory account name as an asterisk, for instance, OneFS processes it as a wildcard. A wildcard matches any name in the field.
Further: If you use a wildcard in the source username and the target username, OneFS expands the wildcard in the target to match the value from the source.
Here are two examples of rules that include wildcards:
Source Username Operator Target Username
* join TESTER\* Œ
*\* replace guest
Œ This rule matches any identity with a UNIX username and expands it to include the user with an Active Directory account of the same name in the TESTER domain. Since a join rule is bidirectional, the rule also matches any identity in the TESTER domain and expands it to match any UNIX user with the same username.
This rule matches any source username in any Active Directory domain and replaces it with the UNIX user named guest.
The following examples contain invalid wildcard-matching rules:
Source Username Operator Target Username
*\jdoe join TEST DOMAIN\*
guest replace *
The first rule leaves a wildcard unmatched in both directions. In the second rule, the replace operator matches left to right, but the wildcard on the right is unmatched, making the rule invalid.