2.17 Securing Cloud Deployment of OpenText Identity Manager Components

You can deploy the components on MicroSoft Azure and Amazon Web Services EC2. While deploying the components on these cloud platforms, you must consider the following security recommendations:

  • The components should be configured on a private network with no public access

  • Web applications such as Identity Applications, Identity Reporting, or OpenText Identity Console should be accessed through an application gateway

  • The components should be configured to use a secured communication channel

  • The following ports should be made available on the OpenText Identity Manager servers to use within the subnet for MS Azure:

    Component

    Port

    Description

    LDAP for Identity Vault

    TCP 636

    Required for the secured LDAP communication.

    Identity Applications

    TCP 8543

    Required for the HTTPS communication to access Identity Applications.

    Identity Reporting

    TCP 8643

    Required for the HTTPS communication to access Identity Reporting.

  • The following ports should be made available on the OpenText Identity Manager servers to use within the subnet for AWS EC2:

    Component

    Port

    Description

    LDAP for Identity Vault

    TCP 636

    Required for the secured LDAP communication.

    Identity Applications

    TCP 8543

    Required for the HTTPS communication to access Identity Applications.

    Identity Reporting

    TCP 8643

    Required for the HTTPS communication to access Identity Reporting.

    PostgreSQL Database

    TCP 5432

    Required for the secured database communication to access PostgreSQL.