Cloud Listeners

Are you interested in deploying your Onum installation in our Cloud? Contact us, and we will configure a dedicated Cloud Tenant for you and your organization.

Overview

If your Onum installation is deployed in our Cloud, the configuration settings of a Listener would be slightly different from Listeners defined in an On-Premise deployment:

• Cloud Listeners do not have the TLS configuration settings in their creation form, as the connection is already secured.

• Cloud Listeners have an additional step in their creation process: Network configuration. Use these details to configure your data source to communicate with Onum. Click Download certificate to get the required certificate for the connection. You can also download it from the Listener details once it is created.

Learn more about the configuration steps of each Listener type in this section.

Important Considerations

You must consider the following indications before using Cloud Listeners:

• When configuring a Listener in a Cloud tenant, note that the selected port must fall within the range of 1024 to 10000.

• Cloud Listener endpoints are created in Onum's DNS. This process is usually fast, and Listeners are normally available immediately. However, note that this may last up to 24-48 hours, depending on your organization's DNS configuration.

• Cloud Listener endpoints can use both Mutual TLS (mTLS) and TLS authentication, which means that your data input must be authorized with a certificate.

• Your data input must use the Server Name Indication (SNI) method, which means it must send its hostname in the TLS authentication process. If SNI is not used, the certificate routing will fail, and data will not be received, even if the certificate is valid.

If your organization's software cannot meet points 2 and 3, you can use an intermediate piece of software to ensure the client-Onum connection, such as Stunnel.