If you need to make any changes to your Custom Subdomain's SSL certificate, such as adding additional domains, you will need to delete your existing certificate and recreate it with the desired changes.
However, before deleting the previous certificate we highly recommend you set our default endpoint as a fallback to your custom subdomain. This will ensure there is no disruption to the identification service while you migrate to the new certificate. Please review the following code snippets for guidance on setting the fallback endpoint:
CDN Installation Method
const fpPromise = import('https://metrics.example.com/web/v3/XXXXXXXXXXXXXXXX')
.then(FingerprintJS => FingerprintJS.load({
endpoint: [
"https://metrics.example.com",
FingerprintJS.defaultEndpoint
]
}))
NPM Installation Method
import FingerprintJS, {
defaultEndpoint,
defaultScriptUrlPattern
} from '@fingerprintjs/fingerprintjs-pro'
const fpPromise = FingerprintJS.load({
apiKey: "XXXXXXXXXXXXXXXX",
endpoint: [
"https://metrics.example.com",
defaultEndpoint
],
scriptUrlPattern: [
"https://metrics.example.com/web/v<version>/<apiKey>/loader_v<loaderVersion>.js",
defaultScriptUrlPattern
]
})
Once you have ensured the fallback endpoint is in place, follow these steps to proceed with recreating your SSL certificate:
- From the Fingerprint dashboard, go to App Settings > Subdomains. Then click the trashcan icon to the right of your current certificate to delete it.
- Once the original certificate has been deleted, you can click add certificate button and set up your new certificate with the desired changes. Please reference this documentation if you need a refresher on setting up your SSL certificate.
Comments
0 comments
Article is closed for comments.