Validations that can be applied to Identity Cloud fields include the following:

• blacklist
• emailDomainBlacklist
• format
• match
• matchOptions
• maxLength
• minLength
• minYears
• required
• unique
• disableClientSide
• alongWith
• whitelist
• clientFunctionName
• serverRegexSetting

blacklist

Enables you to prevent users from using a specified set of words in their data input; for example, you might want to prevent certain words or phrases from being used in a user’s display name. To use this attribute, you must first create an API client setting (e.g., blocked_words) that contains a comma-separated list of all the blocked terms. You then add the rule and set the rule value to the name of the setting.

When assigning this validation by using the Configuration API, your syntax will look similar to this:

{
  "rule": "blacklist",
  "value": "blocked\_words",
  "message": {
    "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
  }
}

This validation can be used with the following field types:

• Text input field

emailDomainBlacklist

Enables you to prevent users from registering for new accounts by using email addresses from a specified set of domains; for example, you might disallow all email addresses from the akamai-documentation-test-site.com domain. To use this attribute, you must first create an API client setting (e.g., email_blocked_setting) that contains a comma-separated list of all the blocked domain names. You then add the rule and set the rule value to the name of the setting.

When assigning this validation by using the Configuration API, your syntax will look similar to this:

{
  "type": "email",
  "name": "emailAddress",
  "schemaAttribute": "email",
  "validation": [
    {
      "rule": "emailDomainBlacklist",
      "value": "email\_blocked\_setting",
      "message": {
        "key": "63f7c18f-521a-4b4f-94c4-0b04b870c82e"
      }
    }
  ]
}

This validation can be used with the following field types:

• Email field

format

Asserts that the field conforms to a specified format. The format validation takes one of the following predefined formats as its value:

When assigning the format validation by using the Configuration API, your syntax will look similar to this:

{
  "rule": "format",
  "value": "email",
  "message": {
    "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
  }
}

The format validation can be used with the following field types:

• Text input field
• Email field
• Password field
• Text area field
• Date select field

match

Asserts that a field value matches the value of another field. The match value must be set to the name of another field. For example, here the value entered for a field must be exactly the same as the value entered in the confirmPasswordField field:

{
  "rule": "match",
  "value": "confirmPasswordField",
  "message": {
    "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
  }
}

The match validation can be used with the following field types:

• Text input field
• Email field
• Password field
• Radio buttons field
• Select menu field

matchOptions

Protects against invalid input on select fields by requiring the value submitted to be one of the options defined in the field. Set this to false only if you plan on dynamically populating the select options yourself. This is added to select fields by default. For example:

{
  "rule": "matchOptions",
  "value": True
}

The matchOptions validation can be used with the following field types:

• Select menu field

maxLength

Asserts that the value of a field has no more than the specified number of characters. For example, this syntax limits the number of characters than can be entered in a field to 30:

{
  "rule": "maxLength",
  "value": 30,
  "message": {
    "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
  }
}

The maxLength validation can be used with the following field types:

• Text input field
• Email field
• Password field
• Text area field

minLength

Asserts that the value of a field must have at least the specified number of characters. For example, this syntax requires the value to contain at least 4 characters:

{
  "rule": "minLength",
  "value": 4,
  "message": {
    "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
  }
}

The minLength validation can be used with the following field types:

• Text input field
• Email field
• Password field
• Text area field

minYears

Asserts that the value from a dateselect field is at least the specified number of years in the past. With the minYears validation you have several options available to you:

• For the validation value, you can specify an integer value.

• Alternatively, you can create an API client setting (e.g., settingNameToSourceFrom) and then set the value of the setting to your minimum years value. You can then use the key parameter to reference the API client setting. By doing this, you can change the minYears value by modifying the client setting, and without having to modify the form.

• You can specify a default value (default) which will be used if the API client setting is not available.

When assigning the minYears validation by using the Configuration API, your syntax will look similar to this. In this example, the validation value is taken from an API client setting named settingNameToSourceFrom. If that setting can’t be found, then the default value of 13 is applied:

{
  "type": "dateselect",
  "name": "childBirthdate",
  "schemaAttribute": "birthday",
  "validation": [
    {
      "rule": "minYears",
      "value": {
        "key": "settingNameToSourceFrom",
        "default": 13
      },
      "message": {
        "key": "63f7c18f-521a-4b4f-94c4-0b04b870c82e"
      }
    }
  ]
}

The minYears validation can be used with the following field types:

• Date select field

required

Asserts that a value is provided for this field; set to true to enable this validation. For example:

{
  "rule": "required",
  "value": true,
  "message": {
    "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
  }
}

The required validation can be used with the following field types:

• Text input field
• Email field
• Password field
• Checkbox field
• Radio buttons field
• Select menu field
• Text area field
• Date select field

unique

Asserts that the value of this field is unique when compared to all records within your Identity Cloud application; set to true to enable this validation. For example:

{
  "rule": "unique",
  "value": true,
  "message": {
    "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
  }
}

The unique validation can be used with the following field types:

• Text input field
• Email field

Using the unique validation, you have the option of including two additional validations: disableClientSide and alongWith.

disableClientSide

When set to true, disables client-side validation, and verifies the uniqueness of a value only when the form is submitted. By default, unique values are checked as they are entered; for example, if a user tries to register by using a previously-used display name, they will be notified of that fact before they click the Create Account button.

If disableClientSide is set to true, however, display name validation will only take place after the user clicks Create Account.

When assigning the disableClientSide validation by using the Configuration API, your syntax will look similar to this:

{
  "type": "text",
  "name": "mobileNumber",
  "schemaAttribute": "mobileNumber",
  "validation": [
    {
      "rule": "unique",
      "value": {
          "disableClientSide": true
      }
      "message": {
        "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
      }
    }

alongWith

Provides a way to verify that the combined value of two fields returns a unique value. For example, there’s no reason why two users can’t have the same phone number (555-555-0712) as long as they have different country calling codes: 591-555-555-0712 is not the same phone as 357-555-555-0712. Using the alongWith validation, you can verify that the combined value of a user’s mobileNumberCountryCode attribute and his or her mobileNumber attribute is unique. This can be done by:

• Specifying mobileNumber as the primary attribute.
• Adding the alongWith validation and specifying mobileNumberCountryCode as the secondary attribute.

For example:

{
  "type": "text",
  "name": "mobileNumber",
  "schemaAttribute": "mobileNumber",
  "validation": [
    {
      "rule": "unique",
      "value": {
         "alongWith": "mobileNumberCountryCode"
       }
      "message": {
        "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
      }
    }

whitelist

Requires users to choose from a specified collection of words when entering data. To use this attribute, you must first create an API client setting (e.g., allowed_words) that contains a comma-separated list of all the allowed words and phrases. You then add the whitelist rule and set the rule value to the name of the setting.

When assigning the whitelist validation by using the Configuration API, your syntax will look similar to this:

{
  "rule": "whitelist",
  "value": "allowed\_words",
  "message": {
    "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
  }
}

The whitelist validation can be used with the following field types:

• Text input field

clientFunctionName

Name of the function to use for client-side validation. Functions are defined in the janrain-init.js file, and the name of that function (e.g., validateUserName) is set as the value of the clientFunctionName validation.

For example:

{
  "rule": "clientFunctionName",
  "value": "validateUserName",
  "message": {
    "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
  }
}

The clientFunctionName validation can be used with the following field types:

• Text input field
• Email field
• Password field
• Select menu field
• Text area field
• Date select field

serverRegexSetting

Specifies the name of an API client setting to be used for validation. For example:

{
  "rule": "serverRegexSetting",
  "value": "serverRegexSetting",
  "message": {
    "key": "8a8508aa-f939-472b-bad2-59f6c0089a60"
  }
}

The serverRegexSetting validation can be used with the following field types:

• Text input field
• Email field
• Password field
• Select menu field
• Text area field
• Date select field