Skip to content
Last updated

Content Security Policy

Embeds rely on style and script elements rendered inside the iframe. If your application uses a Content Security Policy, these elements might be blocked by your rules. To avoid this, permit the following sources in your policy. If you are installing the Checkr WebSDK library via CDN, additionally add the CDN source to the script-src header.

CSP HeaderSources
frame-srchttps://web-sdk-services.checkr.com
script-srchttps://web-sdk-services.checkr.comhttps://cdn.jsdelivr.net/npm/@checkr/web-sdk

If you are using a Checkr staging account, you will need to add sources for Staging as well.

CSP HeaderSources
frame-srchttps://web-sdk-services.checkr-staging.com
script-srchttps://web-sdk-services.checkr-staging.comhttps://cdn.jsdelivr.net/npm/@checkr/web-sdk

cspNonce

cspNonce can be used to pass a nonce to all inline style elements rendered by Embeds.

Note: Nonces should be generated differently each time the page loads and should be a random base64-encoded string of at least 128 bits of data from a cryptographically secure random number generator. If your site uses static html, consider using a CSP hash instead.

const crypto = require('crypto')
const cspNonce = crypto.randomBytes(16).toString('base64') // '8IBTHwOdqNKAWeKl7plt8g=='

const embed = new Checkr.Embeds.NewInvitation({ cspNonce })