{"id":23754,"date":"2022-09-07T09:26:23","date_gmt":"2022-09-07T09:26:23","guid":{"rendered":"https:\/\/refiner.io\/docs\/?post_type=knowledgebase&p=23754"},"modified":"2026-09-03T16:06:55","modified_gmt":"2026-09-03T16:06:55","slug":"identity-verification","status":"publish","type":"knowledgebase","link":"https:\/\/refiner.io\/docs\/kb\/data-index\/identity-verification\/","title":{"rendered":"Identity Verification"},"content":{"rendered":"\n\n\n

Introduction<\/h2>\n\n\n\n

IIdentity Verification is an additional security mechanism that protects your Refiner installation from unauthorized third-party requests.<\/p>\n\n\n\n

It prevents third parties from impersonating your users or creating bogus user profiles by requiring requests to include a cryptographic signature that only your backend can generate.<\/p>\n\n\n\n

We highly recommend enabling Identity Verification in production environments.<\/p>\n\n\n\n

How Identity Verification works<\/h2>\n\n\n\n

When Identity Verification is enabled, requests involving an identified user must include a valid signature for that user.<\/p>\n\n\n\n

The signature is unique to each user and is generated on your backend using the user’s identifier and a Refiner API key.<\/p>\n\n\n\n

Requests without a user identifier or with an invalid signature are rejected by Refiner.<\/p>\n\n\n\n

Because the signature can only be generated by someone with access to your API key, third parties cannot simply use your Environment ID to impersonate users or create bogus user profiles.<\/p>\n\n\n\n

Note:<\/strong> Identity Verification requires a unique identifier for each user. When enabled, the JavaScript SDK cannot be used in Anonymous Mode<\/a>, and Survey Links<\/a> must include a user identifier.<\/p>\n\n\n\n

Enable Identity Verification<\/h2>\n\n\n\n

Open the Identity Verification settings in your Refiner environment and enable verification for the survey channels where you want to enforce it.<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

You can initially leave Identity Verification disabled while implementing and testing signatures. Refiner will validate signatures when they are provided but will continue to accept requests without one.<\/p>\n\n\n\n

Once your implementation is working correctly, enable Identity Verification to reject unsigned requests.<\/p>\n\n\n\n

Create an API key<\/h2>\n\n\n\n

Go to Settings > API Keys<\/strong> and create an API key<\/a> that will be used to generate Identity Verification signatures.<\/p>\n\n\n\n

We recommend creating a dedicated API key for Identity Verification rather than sharing a key with other integrations.<\/p>\n\n\n\n

Important:<\/strong> Your API key is a secret and must only be used in your backend. Never expose it in frontend JavaScript, HTML, a public code repository, or any other client-side code.<\/p>\n\n\n\n

Compute the signature<\/h2>\n\n\n\n

The Identity Verification signature is an HMAC<\/a> generated using SHA-256.<\/p>\n\n\n\n

Use the user’s identifier as the message and your Refiner API key as the secret key.<\/p>\n\n\n\n

The USER_ID<\/code> must be the same identifier you later use when identifying the user with Refiner.<\/p>\n\n\n\n

For testing purposes, you can keep Identity Verification in your Refiner settings disabled (see above). When disabled, Refiner will validate provided signatures, but also accept requests without a signature.<\/p>\n\n\n\n

\n

Node.js<\/strong><\/p>\n\n\n\n

import crypto from 'crypto'\n\nlet signature = crypto.createHmac('sha256', 'SECRET_KEY').update(USER_ID).digest('hex')<\/pre>\n\n\n\n
PHP<\/strong><\/p>\n\n\n\n
$signature = hash_hmac('sha256', $userId, 'SECRET_KEY')<\/pre>\n\n\n\n
Ruby<\/strong><\/p>\n\n\n\n
signature = OpenSSL::HMAC.hexdigest('sha256', 'SECRET_KEY', USER_ID)<\/pre>\n\n\n\n
<\/p>\n<\/div><\/div>\n\n\n\n
Pass the signature to Refiner<\/h2>\n\n\n\n
Once generated on your backend, pass the signature together with the user’s identifier when identifying the user.<\/p>\n\n\n\n
JavaScript SDK<\/h3>\n\n\n\n
Pass the computed signature to the identifyUser<\/a><\/code> method as described in our JavaScript Client Reference.<\/p>\n\n\n\n
If you use our Google Tag Manager<\/a> installation, provide the signature as a user trait using identify_verification_signature<\/code> as the field identifier.<\/p>\n\n\n\n
Mobile SDK<\/h3>\n\n\n\n
Pass the computed signature as an additional parameter to the identifyUser<\/a><\/code> method.<\/p>\n\n\n\n
Refer to the SDK documentation for detailed implementation instructions:<\/p>\n\n\n\n