Gigya Job Openings

Encrypted Fields

Skip to end of metadata
Go to start of metadata

The account.search and ids.search APIs allow searching using "contains" on unencrypted text (string) fields. The "contains" operand is not case sensitive, but if you want to perform a search on an encrypted field, you must enter a full string. In addition, you cannot use the order by clause on encrypted fields.

Encrypted fields include any text fields you defined as encrypted in your schema and also the fields listed here: 

  • profile.address
  • profile.email
  • profile.firstName
  • profile.lastName
  • profile.name
  • profile.phones
  • profile.shippingAddress
  • identities.address
  • identities.email
  • identities.firstName
  • identities.lastName
  • identities.name
  • identities.phones
  • identities.shippingAddress
  • identities.username
  • loginIDs.emails
  • loginIDs.username
  • loginIDs.unverifiedEmails
  • emails.unverified
  • emails.verified

 

Once a field is saved as encrypted, the process cannot be reversed.