When running Collibra Platform, the following limitations apply:
- Integrations:
- Connecting to your company's LDAP server is only possible if the LDAP server is accessible from external servers.
- Sending emails is always done through the Collibra SMTP server using Mailgun.
Tip If you filter on your mail server either by DNS name or IP, look at the from values in the Received field for the domain and IP, for example
cloud-mail.collibra.com. [198.2.180.134]. - Workflow action emails requires Collibra to connect to an IMAP or POP server. When requested, Collibra can setup a private email address for you.
- Custom domains and certificates:
- Collibra does not support using a custom domain or SSL certificate for the URL of the cloud environment. However, you can use a custom proxy server on your side.
- Product updates:
- Collibra automatically applies product updates when necessary.
- Guest access:
- Guest access is not supported in the cloud environment because the cloud environment is publicly accessible.
- HTTP methods
- The HTTP PATCH method is not supported in Collibra environment. Instead, you can use the POST method with an
X-HTTP-Method-Overrideheader.
- The HTTP PATCH method is not supported in Collibra environment. Instead, you can use the POST method with an
- Azure Application Gateway upload limitation:
- Microsoft Azure Application Gateway has a limitation of 4 GB on uploads. As a result, backups larger than 4 GB cannot be uploaded. We are actively investigating solutions to address this limitation.