Limitations

Running Collibra Platform has a couple of limitations:

• Integrations: Connecting to your company's LDAP server is only possible if the LDAP server is accessible from the outside world (from our servers).
• Sending emails is always done through the Collibra SMTP server. For this we use mailgun.
  When receiving emails from your cloud environment, you see the following:
  

  Example Received: from cloud-mail.collibra.com (cloud-mail.collibra.com. [198.2.180.134])

  This can be used to filter on your mail server (either by DNS name or IP).
• Workflow action emails requires Collibra to connect to an IMAP or POP server. When requested, Collibra can setup a private email address for you.
• Collibra does not support a custom domain or SSL certificate to be used for the URL of the cloud environment.
  To solve this, a custom proxy server can be used on the customer side.
• Collibra automatically applies product updates when necessary.
• Because the cloud environment are publicly accessible, guest access is not possible in the cloud environment.
• On a Collibra Platform environment, you cannot use the HTTP method PATCH.

  Use the HTTP method POST with X-HTTP-Method-Override header instead.

• Microsoft Azure Application Gateway has a limitation of 4 GB on uploads. Therefore, we can only upload backups with a maximum size of 4 GB. We are looking for solutions to work around this limitation.