FAQ about IT and server deployments

• Can we install the SQL database for memoQ TMS in a subcluster?

  Yes, but test the deployment first to check if database permissions match your IT policy.

• Can we deploy memoQ TMS in a DMZ?

  Yes, but test the deployment first because it can depend on your local IT architecture.

• Can we use proxy for memoQ?

  Yes.

• Can we use a load balancer?

  memoQ TMS server does not support load-balancing.

  Some configurations can improve performance:

  • memoQ TMS performance can be adapted for high availability usage by adjusting the number of worker threads.

  • You can run the memoQ TMS server, SQL server, and IIS on separate machines.

• Can we use IP-filtering when working with APIs and users?

  Yes, IP filtering is available for the Web Services API. User access can be controlled by whitelisting at the network firewall level.

• Can we configure the port which memoQ uses for communication between the client and server?

  Yes, memoQ TMS public cloud communicates over TCP 2705 by default. However, if you’d like to use a different port, this can be configured for on-premise or memoQ TMS private cloud deployments.

• Can we use Active Directory for single sign-on user management?

  Yes, if memoQ TMS is running on a server within the same domain as your Active Directory.

• Can we use Azure AD for single sign-on user management?

  Yes, if OIDC is enabled and this is used for SSO.

• Can we use Open ID Connect (OIDC) for single sign-on user management?

  Yes, various identity providers that fully support the standard OIDC protocol are supported.

• Is SAML supported?

  No, SAML is currently not supported. We only support OIDC-based identity providers.

  However, some IDPs support both SAML and OIDC protocols. First, check if that’s true for your case, and then we can see if it would be possible to work with the OIDC protocol instead.

• Should we allow outbound or inbound communication requests?

  For using memoQ client, outbound is sufficient.

  However, for memoQ server and memoQweb, inbound communication requests need to be enabled.

• Which ports does memoQ use?

  Ports can be changed in on-premise and memoQ TMS private cloud deployments.

  Ports memoQ use:

  • 2705 TCP or 443 HTTPS for server-client connection

  • 8080-8082 TCP for API

  • 5001 TCP for OIDC

  • 2100-2121 TCP for FTP

  • 80 TCP for standalone license activation

    For on-premise deployments of the memoQ TMS server, TCP port 80 is used for license credential renewal (not relevant for server/cloud deployments). This port restriction cannot be changed. In special cases, you can work around this problem by obtaining a one-time license that must be renewed every year.