Collibra Console configuration

The duration in milliseconds before the Jobserver service startup is considered as a failure.

The default value is 300,000 milliseconds or 5 minutes.

The duration in milliseconds before the Repository service startup is considered as a failure.

The default value is 300,000 milliseconds or 5 minutes.

The password used to sign in to the SMTP server.

A password is not required.

The email address used as the sender of all outgoing emails.

See Email configuration for Collibra Data Intelligence Platform and Collibra Console to update this setting in cloud environments.

The port used to access the SMTP server.

The default port is 25.

Allow LDAP users to have the Collibra Console SUPER role. The default value is false, any LDAP users with SUPER role will have same access rights as ADMIN role users.

Maximum time in milliseconds for LDAP search operations.

The default value is 120,000 milliseconds or two minutes.

Set it to 0 if you do not want a time limit.

When using SSL, use the LDAP's protocol and use the correct port.

The SSL section in the configuration should also be configured for this.

LDAP authentication mechanism; must be one of the following:

• none: No authentication is performed.
• simple: Simple authentication is performed, using the Bind DN and Bind password as credentials. The credentials are sent as plain text.
• DIGEST-MD5: Simple authentication is performed using the Bind DN and Bind password as credentials. The Bind password is hashed with the MD5 algorithm.
• TLS-SIMPLE: A temporary secured TLS connection is set up before the credentials are sent as plain text. SSL must be configured.
• TLS-EXTERNAL: A temporary secured TLS connection with external SASL authentication using a client certificate. SSL must be configured.

Note When using TLS, dont forget to configure the SSL security section.

Specifies how referrals should be handled; must be one of:

• throw
• ignore
• follow

The attribute to define that users are member of a group, for example uniqueMember. This field is mandatory when mapping LDAP groups to roles.

The mapping of the LDAP users that are members of the group with a specified DN to a role.

Role mapping is mandatory for LDAP to be enabled. This is the LDAP directory field that defines which console role the user should have. If you do not intend on using this configuration mapping use the default mapping of role.

• True (default): The CSS files are optimized to improve performance of the user interface.
• False: The CSS files are not optimized.

• True (default): The JavaScript code is optimized to improve the performance of the user interface.
• False: The JavaScript code is not optimized

• True (default)
• False

• True: The velocity cache is enabled.
• False: The velocity cache is disabled. This allows you to reload velocity templates without restarting Collibra.

The duration in milliseconds before the creation of a backup is considered as a failure.

The default value is 43,200,000 milliseconds or 12 hours.

During an upgrade, this value is also taken into account.

The number of times an automated retry will be attempted after encountering the initial backup error.

The default value is 1.

Time in milliseconds between retry attempts.

The default value is 5,000 milliseconds.

The SSO mode of Collibra Console. Collibra Console only supports SAML_ATTRIBUTES.

When SSO is enabled, a user can still navigate to the /signin page and try to log in via that page. However, you can disable that page.

• True: Users cannot access the Collibra Console signin page.
• False (default): Users can access the Collibra Console signin page

The default role for all SSO users. The default role is READ.

SSO users with a SUPER role will be downgraded to users with the ADMIN role. Only a Collibra Console SUPER user can enable the SUPER role for SSO users.

• True: SSO users can have the SUPER role.
• False (default): SSO users with the SUPER role will be downgraded to users with the ADMIN role.

This option is only visible if you have the SUPER role.

The entity ID inside the metadata to be referenced.

Note A metadata file can describe multiple entity IDs, make sure to use in the entity ID from the correct metadata file.

By default, this URL is the same as the URL of your Collibra environment but if your IDP expects another value, you can fill it out here.

Warning Make sure that the intended destination endpoint (The Destination attribute in the SAML response) matches the URL being used here. So this is only to be used in specific IDP circumstances When setting this, and getting the error "SAML message intended destination endpoint did not match recipient endpoint" check the Destination attribute in your SAML response and this parameter.

• True: The validation of the client IP address in the assertion message is disabled.
• False (default): The validation of the client IP address in the assertion message is enabled.

• True: Authentication requests have to be signed. Use a Collibra generated self-signed certificate to sign requests. The request that is generated by Collibra Console will be appended with a signature in the redirect URL of the response.
• False (default): Authentication request don't have to be signed.

• True (default): The SP authentication request forces re-authentication.
• False: The SP authentication request does not force re-authentication.

Configure whether the SP authentication should set the authentication to go passive.

If True, the IDP or browser MUST NOT take visibly control of the user interface. See the SAML 2.0 specification for more details.

This is only relevant if Force authn is True.

Configure the nameID used in the SP authentication. If set, the full content will be sent as a nameID. Use a fully qualified nameID.

Default nameID="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent". See SAML 2.0 specification for accepted nameID values.

The mapping for the user's username. The value of this attribute must be the name of the SAML attribute as defined in your IDP.

In the following example, the value in Collibra Console must be email. This is the used name in your IDP software, see the following screenshot.

This field is mandatory.

The mapping for the user roles. The value of this attribute must be the name of the SAML attribute as defined in your IDP.

In the following example, the value in Collibra Console must be role. This is the used name in your IDP software, see the following screenshot.

The mapping to define which attribute holds group information. The value of this attribute must be the name of the SAML attribute as defined in your IDP.

In the following example, the value in Collibra Console must be groups. This is the used name in your IDP software, see the following screenshot.

If there is more than one group attribute statement, add them as comma-separated list.

Specifies the comparison method used to evaluate the requested authentication context. One of: "exact", "minimum", "maximum", "better".

The industry default is "exact", other options are "minimum", "maximum" and "better".

• Exact: The authn context in the assertion MUST exactly match the full expected context specified on the SP.
• Minimum: The authn context in the assertion MUST be at least as strong as one of the contexts specified on the SP.
• Better: The authn context in the assertion MUST be stronger than any of the contexts specified on the SP.
• Maximum: The authn context in the assertion MUST be as strong as possible for all of the contexts specified on the SP, without exceeding the strength of at least one context.

For more details, see the SAML 2.0 specification (Section 3.3.2.2.1).

The pattern of the URLs to which the HTTP response header is applied.

This field supports wildcards such as **, *, and ?.

Tip The following pattern matches all URLs: /**