Page History
Sv translation | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Parameters in |
Parameter name | Description |
---|---|
| Specifies the URL on which is BellaDati running. The default value is http://localhost. |
| Determines whether BellaDati is running in production mode. The default value is |
| Determines whether BellaDati is running in SSL/TLS mode. If set to |
| JDBC driver used by BellaDati for database connections. Currently, only |
| If you don't have a JNDI data source configured, you can use the |
| Username used by BellaDati to access the database. This parameter is used only when |
| Password used by BellaDati to access the database. This parameter is used only when |
| Maximum number of active database connections. |
| Minimum number of database connections in idle state. |
| Maximum number of database connections in idle state. |
| Name of the JNDI resource to access the database, e.g. |
| URL of the SMTP server used for sending email. Default value is |
| SMTP server port. Default value is |
| Determines whether SSL is used for SMTP. Default value is |
| Username for accessing the SMTP server. |
| Password for accessing the SMTP server. |
| This parameter allows you to change the email sender address. |
| The value of this parameter is automatically appended to all outgoing emails. The default value is |
| Specifies the directory for report and data set indexes. Default value is |
| Consumer application ID for the Facebook connector. |
| Consumer application secret for the Facebook connector. |
| Consumer key for the Twitter connector. |
| Consumer secret for the Twitter connector. |
| Consumer key for the SalesForce connector. |
| Consumer secret for the SalesForce connector. |
core.membersLimit | Note that by increasing default value from 1000 to larger values. Users can use Attribute Looping Functions exp. eachMember() on larger datasets. Important: read best practices. You may need higher hardware configuration especially for multi-tenant BellaDati environment. |
core.joins.limit | Rows limit of the maximum join size |
core.joins.previewLimit | Joins preview limit - sometimes it is reasonable to use just the preview instead of materializing the join |
If you change the lucene.indexes parameter on a system that's already in use, you will need to reindex your reports and data sets. After restarting the server and logging in, move the mouse over your username and click the link to your domain. On the left side, reindex your reports and data sets.
ActiveDirectory/LDAP Authentication
Tip |
---|
Since version 2.7.9.1 you can configure the ActiveDirectory authentication directly from the user interface. See Setup Active Directory Authentication. |
BellaDati supports customizable authentication providers. Among the basic providers is the Active Directory and LDAP authentication provider. To enable this authentication provider, follow the instructions below:
BellaDati v2.7.4.1 and higher
1. Unzip the WEB-INF/classes/conf/application.properties
configuration file from the BellaDati WAR file or edit the WEB-INF/classes/conf/application.properties in your BellaDati installation directory.
| List of authentication domains - names are displayed on the login page. E.g. |
| Determines whether accounts that don't exist are automatically created. |
| Specifies the |
| Specifies the search URL, e.g. LDAP://adhost:389/OU=Unit,OU=test,DC=company,DC=com |
| The |
| The password of the user with search permission. |
| The login attribute, e.g. |
2. If you have extracted the application.properties file from belladati.war
archive, update this archive.
BellaDati v2.7.4 and below
1. Unzip the WEB-INF/classes/conf/beans-common.xml
configuration file from the BellaDati WAR file.
2. Replace the bean
element with id="userAuthenticityProvider"
with this content:
Code Block | ||||
---|---|---|---|---|
| ||||
<bean id="userAuthenticityVerifier" class="cz.trgiman.belladati.auth.ADUserAuthenticityVerifier" autowire="byType"> <property name="createNotExistingAccounts" value="true"/> <property name="workspaceId" value="1"/> <property name="domains"> <map> <entry> <key><value>domain1</value></key> <bean class="cz.trgiman.belladati.auth.DomainSpecification"> <property name="url" value="LDAP://host1:389/dc=xyz"/> <property name="bindDN" value="bindUser"/> <property name="bindPassword" value="bindUserPassword"/> <property name="loginAttribute" value="sAMAccountName"/> <property name="workspaceId" value="1"/> </bean> </entry> <entry> <key><value>domain2</value></key> <bean class="cz.trgiman.belladati.auth.DomainSpecification"> <property name="url" value="LDAP://host2:389/dc=xyz"/> <property name="bindDN" value="bindUser2"/> <property name="bindPassword" value="bindUserPassword2"/> <property name="loginAttribute" value="cn"/> <property name="workspaceId" value="1"/> </bean> </entry> </map> </property> </bean> |
3. Add the following parameter to the WEB-INF/classes/conf/application.properties
file:
Code Block |
---|
application.login.domains=domain1,domain2 |
4. Update the belladati.war
archive.
...