Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. Hierarchies Upgrade
  13. ActiveVOS Post-Installation Tasks for the Application Server
  14. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  15. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  16. Appendix A: Troubleshooting the Upgrade Process
  17. Appendix B: Frequently Asked Questions
  18. Appendix C: Processing Existing ActiveVOS Tasks
  19. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Customize the Content Security Policy

Customize the Content Security Policy

Content Security Policy (CSP) is a standard that prevents code injection attacks, such as cross-site scripting. A website declares approved origins of content that a browser can load to display website content. The upgrade process checks for custom user interface components in the registered Operational Reference Store (ORS) databases. If any components are found, the appropriate content security policy is applied to ensure that no custom interface components are blocked.
If custom user interface components are found, the content security policy is set to the defaults required for Multidomain MDM to function. The upgrade process then adds the following rules:
script-src *; font-src *; style-src *; frame-src *; image-src *; default-src *;
After you upgrade, customize the content security policy to secure your system and prevent code injection attacks. For more information about configuring the content security policy, see the
Multidomain MDM Provisioning Tool Guide
.

0 COMMENTS

We’d like to hear from you!