Proxy settings

    ManageEngine SecureAI connect to services outside your network to do its work. Where your organization requires that traffic to pass through a proxy server, proxy settings tell SecureAI which proxy to use and which credentials to present to it. Outbound connections then follow the route your network team permits. Configure proxy settings when SecureAI is installed behind a proxy. Return to them when the proxy address, port, or password changes or when your organization stops routing traffic this way.

    How it works

    SecureAI runs on a server in your network and connects out to the platforms it manages, to ManageEngine services for licensing and product updates, and to your mail service for the email it sends. When a proxy is enabled, SecureAI routes these connections to the proxy server and port you supply, and the proxy forwards them to their destination. SecureAI also presents a username and password to the proxy when the proxy asks its clients to authenticate. A proxy that authorizes by source address requires neither value, allowing both to be left empty. During the connection test, the values entered at that moment are used, whether or not they have been saved, so you can check a configuration before you apply it. The test establishes whether the proxy answers at the address given, which is a more specified inquiry than whether the proxy forwards everything SecureAI needs.

    Prerequisites

    Complete the following before you configure proxy settings:

    • Log in with a role that includes the Server Settings permission under Administration. In SecureAI, both Super Admin and Governance Manager roles include this permission.
    • Obtain the hostname or IP address of the proxy server and the port it listens on.
    • Confirm that the SecureAI server can reach the proxy on that port and through any firewall between them.
    • Where the proxy authenticates its clients, obtain the username and password of an account permitted to use it.
    • Ask the team that runs the proxy to permit the destinations SecureAI connects to, including the platforms it manages, the ManageEngine licensing and update services, and your mail service, so that its traffic is forwarded rather than refused.
    Note:
    • SecureAI holds one proxy configuration and applies it to the whole installation. Separate proxies for individual platforms, accounts, or connections are not available.
    • There is no option to exclude specific addresses. Once the proxy is enabled, all outbound connections go to it.
    • Only one proxy address is accepted. A second address cannot be entered as a fallback.
    • The proxy requires a username and password for authentication. Certificate-based and token-based authentication are not offered.

    Configuration instructions

    1. Navigate to Settings > Server Settings > Proxy Settings.
    2. Turn on Enable Proxy Server.
    3. In the Proxy Server/Port field, enter the hostname or IP address of the proxy server and the port it listens on. Both are required once the proxy is enabled.
    4. In the Username and Password fields, enter the credentials of an account permitted to use the proxy. Leave both empty where the proxy does not authenticate its clients.
    5. Click Test Connection and confirm the result before you continue.
    6. Click Save Changes. The configuration applies as soon as it is saved. SecureAI does not need to be restarted.

    Turn off Enable Proxy Server to stop routing SecureAI's outbound connections through the proxy.

    Tips

    • A connection test that succeeds confirms that the proxy answered, not that it forwards every destination SecureAI uses. Where syncs still fail with the proxy in place, ask the team that runs it whether those destinations are permitted.
    • Give SecureAI a service account on the proxy rather than an administrator's own credentials. The configuration then survives staff changes, and a personal password change does not break it.
    • Because SecureAI keeps its own copy of the proxy credentials, password changes on the proxy do not reach it. Update the credentials in your proxy settings in SecureAI at the same time, or outbound connections will start failing. If connections to a platform stop working soon after the proxy is enabled, or if a test email stops arriving, treat the proxy as the likelier cause before you revisit the platform or mail credentials.
    • Where connections to a platform stop working soon after the proxy is enabled, or a test email stops arriving, treat the proxy as the likelier cause before you revisit the platform or mail credentials.
    • A proxy that inspects encrypted traffic presents its own certificate to SecureAI, so confirm with your network team whether inspection is in place before you troubleshoot a connection further.
    • Email delivery, connection type, and each platform's own connection are configured separately and proxy settings do not change them.