The two different keys have been provided to you during the DataDome setup, on this screen you could have access to them when needed.
If you want to get new keys, please contact the support team.
To be notified as soon as possible when your endpoints are under attack, you can use a DataDome Webhook to receive Attack Notifications in your existing third-party services.
You can find all steps required for all our supported integration in our dedicated section Webhook/Notification Integration]
This feature is available for Corporate and Enterprise plans. Please reach DataDome team for more information.
If you want to enable the log enrichment to integrate them in your own tools, you could do it on this screen.
For more information about the integration, please visit Logs Integration.
Let's Encrypt CA compatibilty awareness
Your CAA DNS record for the root domain of your First Party JS Tag domain should allow Let's Encrypt to issue SSL certificates for your root domain.
You should be ok with using Let's Encrypt:
- Let's Encrypt only offers basic DV (Domain Validation) SSL certificates
- Let's Encrypt doesn't offer OVs (Organization Validation) and EVs (Extended Validation) SSL certificates
- Some platforms may have compatibility issues
- Geographic/political reasons may prevent Let's Encrypt from issuing an SSL Certificate for your First Party Js Tag Domain
This should be a non-issue in 99% of the cases, but if you're not sure with Let's Encrypt compatibility on your side you should ask your System Administrator.
First-Party JS Tag deletion
To delete a First-Party JS Tag, please contact the support team.
If you need to host your script in-house you can configure a First-Party JS Tag by following the 4 steps.
When closing this pop-in you will see the status directly in the page.
When the activation is finished you will see the status updated in the page.
Updated about 1 month ago