Home › Discussions › Questions & Answers › Configuring TLS for Oracle Enterprise Command Center Framework

Configuring TLS for Oracle Enterprise Command Center Framework

Avatar photoCustomer Questions & Answers 7 replies

Security audits require us to ensure all communication to and from the Oracle Enterprise Command Center (ECC) Framework and the Integrated SOA Gateway (ISG) uses secure protocols. What steps are required to configure TLS/HTTPS for the ECC Framework?

7 replies

  • Support Enginatics

    Configuring TLS/HTTPS for the ECC Framework is essential for security. This process involves specific steps to secure the communication channel, ensuring data integrity and confidentiality between EBS and the ECC components. ECC TLS/HTTPS with EBS configuration references are available in our technical posts.

  • Avatar photoCustomer

    We also rely on ISG for custom integrations. Are the steps for configuring TLS/HTTPS for the Integrated SOA Gateway similar, and are there different procedures for EBS 12.1 and 12.2?

  • Support Enginatics

    The requirement to secure ISG communications is also critical. We provide detailed instructions for configuring TLS/HTTPS for Oracle EBS Integrated SOA Gateway (ISG) in both EBS 12.1 and EBS 12.2 environments. While the goal is the same, the underlying architectural differences between 12.1 and 12.2 may necessitate slightly different steps.

  • Avatar photoCustomer

    Given the importance of securing the EBS application tier, especially in 12.2 with its layered architecture, how does enforcing HTTPS protect against general attacks through HTTP?

  • Support Enginatics

    Enforcing HTTPS protects your EBS 12.2 environment from various security risks associated with unencrypted HTTP traffic. This is part of the larger strategic recommendation to maintain modern security postures, including proper configuration of components like ECC and ISG, which can be vulnerable if left unsecured.

  • Avatar photoCustomer

    If we enable HTTPS/TLS across all these components, does that affect the functioning or deployment method of Blitz Report?

  • Support Enginatics

    Blitz Report is designed to work within standard, secure EBS environments. Its execution via Forms and the Concurrent Manager remains unaffected, as it continues to use the standard EBS infrastructure (including JWS where applicable). Securing your communication layers (ECC, ISG, core EBS) is a necessary prerequisite for overall operational security.

  • You must be logged in to reply to this post.