The Configure Application tool, added in TeamForge 17.4, makes TeamForge site level settings configurable via the user interface. This comes in handy for site administrators, who otherwise would have to work with the
site-options.conffile and then recreate the TeamForge runtime for site level configuration changes.
To modify your site settings, select My Workspace > Admin and select Projects > System Tools > Configure Application, modify the available site settings as required and click Save.
Project setting(s) that apply globally to all the projects in your TeamForge site:
ALLOWED DOMAINS FOR CSRF
TeamForge administrators can now prevent CSRF by setting listing the domains that are allowed for CSRF.
The ALLOWED DOMAINS FOR CSRF parameter specifies the list of allowed domains to prevent users from performing any CSRF related activities. This list of domains is validated against the origin and the referer headers for any incoming requests into TeamForge. This is helpful while configuring TeamForge for cross-origin requests. The default value is “*” which allows all types of domains or URLs. Example URLs/domains: forge.collab.net, forge.collab.net/sf/sfmain/do/home.
NOTIFY ASSOCIATION AND DEPENDENCY UPDATES
Notification emails can be sent to all monitoring users when an association or dependency is added to an object. You can select the NOTIFY ASSOCIATION AND DEPENDENCY UPDATES check box to let TeamForge send notification emails to all monitoring users when an association or dependency is added. Clear this check box otherwise.
PROHIBITED FILE TYPES
You can restrict users from uploading specific file types. Add a list of comma-separated file extensions in this field to prevent those file types from being uploaded. For example, adding “exe,jar” prevents
.jar files from being uploaded to TeamForge.
Tracker setting(s) that apply globally to all the trackers in your TeamForge site:
MASS IMPORT ARTIFACTS LIMIT
You can restrict the number of artifacts that can be mass-imported. Type the maximum number of artifacts that you want to allow via mass import in the MASS IMPORT ARTIFACTS LIMIT text box.
These settings are tied to any external authentication.
ALLOW DATABASE AUTHENTICATION IF LDAP IS ENABLED
Select this check box to have LDAP credentials stored in TeamForge and have users authenticated via TeamForge every time a user logs in. This helps improve performance by optimizing the number of authentication calls between TeamForge and LDAP servers.
FORCE RE-AUTHENTICATION WITH LDAP SERVER
If you have enabled database authentication, LDAP user credentials are stored when users login for the first time and continue to login using the locally stored LDAP credentials. However, you can restrict such indefinite usage of the stored LDAP credentials and force user re-authentication at regular intervals by setting up this configuration parameter. For example, setting a value of
24 would force user re-authentication (by the LDAP server) every 24 hours.
LDAP CONFIGURATIONS MAXIMUM LIMIT
You can use this parameter to set the maximum number of LDAP configurations to be allowed on sites with multiple LDAP servers/directories. For example, if you set the value as 10, you can add only up to 10 LDAP configurations.
ALLOW LOCAL USER
On sites with LDAP/SAML/SAML+LDAP integrations, site administrators can designate select users that do not have a SAML or LDAP account as local users. Local users can log on to TeamForge using just the TeamForge credentials while bypassing the SAML/LDAP/SAML+LDAP authentication realms. A local user can also change and reset his password.
When you select this ALLOW LOCAL USER site setting, the Create User and Edit User Information pages let site administrators to select the Local User check box while creating or editing user accounts.