About Security Strategies for Oracle Content Management Integrations

Oracle Content Management integrations should provide access to sensitive data only to authorized and authenticated users.

When you design your application to work with Oracle Content Management, consider the following:

  • The Oracle Content Management user typically has full create, read, write, and delete access to all folders and documents created through an integration. Therefore, the user’s credentials should be securely handled.
  • When you use the AppLink feature of Oracle Content Management, limit the folder views in an integrated SaaS service such as Oracle Sales to only the views necessary for the application to function.
  • Web traffic should use HTTPS on port 443 by default.
  • When you embed the Oracle Content Management user interface as an iFrame into another SaaS application such as Oracle Sales, generate web content from a symbolic URL on the SaaS server, and use HTML5 compliant pages in the iFrame.