AppSuite:Configuration properties 7.6.2 - Revision history

Antje at 07:10, 9 July 2015

2015-07-09T07:10:06Z

← Older revision		Revision as of 07:10, 9 July 2015
Line 1,426:		Line 1,426:
	\| <nowiki># Indicates whether to create the confirmed-spam folder during check for default mail folders # during login if spam is enabled for logged-in user. # Default is true. </nowiki>		\| <nowiki># Indicates whether to create the confirmed-spam folder during check for default mail folders # during login if spam is enabled for logged-in user. # Default is true. </nowiki>
	\| defaultspamhandler.properties:6		\| defaultspamhandler.properties:6
	\|-
	~~\| <nowiki>com.openexchange.documentconverter.urlLinkLimit</nowiki>~~
	~~\| <nowiki>true</nowiki>~~
	\| <nowiki># The external URL link limit specifies the maximum amount of valid external internet URLs (filtered by blacklist and whitelist before), that are tried to get resolved by the engine when loading a document. When this limit is reached, no more external internet URLs are resolved for the current document. This limit is not directly related to the amount of visible linked objects within the document. The code itself often needs to resolve one URL more than once or even twice to finish loading of the objects' content. The URL link limit not only affects the amount of URLs, resolved within the viewer but also the amount of resolved URLs when printing or downloading a document, so that the appearance of a viewed and of a printed/downloaded document is similar in general. Set to -1 for no upper limit or to 0 to disable the resolving of internet URLs completely # Default value is 200. </nowiki>
	~~\| documentconverter.properties~~
	\|-		\|-
	\| <nowiki>com.openexchange.capability.drive</nowiki>		\| <nowiki>com.openexchange.capability.drive</nowiki>

Antje at 12:16, 8 July 2015

2015-07-08T12:16:56Z

@@ Line 1,561: / Line 1,561: @@
 | <nowiki>The API key </nowiki>
 | dropbox.properties:7
 |-
 | <nowiki>com.openexchange.mobile.configuration.urlencoding</nowiki>

Antje at 11:37, 8 July 2015

2015-07-08T11:37:08Z

← Older revision		Revision as of 11:37, 8 July 2015
Line 4,821:		Line 4,821:
	\| <nowiki></nowiki>		\| <nowiki></nowiki>
	\| <nowiki>That property allows to specify (wildcard notation supported) those remote addresses/IPs which are excluded from the rate limit checks. Default value is empty. </nowiki>		\| <nowiki>That property allows to specify (wildcard notation supported) those remote addresses/IPs which are excluded from the rate limit checks. Default value is empty. </nowiki>
			\| server.properties
			\|-
			\| <nowiki>com.openexchange.preview.thumbnail.blockingWorker</nowiki>
			\| <nowiki>false</nowiki>
			\| <nowiki> The backend either delivers a thumbnail when it's available from cache or fails fast while initiating the thumbnail creation/caching in the background. The advantage is that clients aren't blocked and can simply retry later when the thumbnail can be delivered from cache.
			If there is no cache configured for the user/context:
			We either have to generate the thumbnail on the fly which has the potential to block the whole client by occupying the max number of allowed connections to the domain or simply fail fast which leaves the client responsive but without thumbnails
			Default value is "false" to keep the client responsive. </nowiki>
	\| server.properties		\| server.properties
	\|-		\|-

Antje at 09:37, 8 July 2015

2015-07-08T09:37:43Z

← Older revision		Revision as of 09:37, 8 July 2015
Line 5,701:		Line 5,701:
	\|-		\|-
	\| <nowiki>com.openexchange.oauth.xing</nowiki>		\| <nowiki>com.openexchange.oauth.xing</nowiki>
	\| <nowiki>~~true~~</nowiki>		\| <nowiki>false</nowiki>
	\| <nowiki>Enable/disable </nowiki>		\| <nowiki>Enable/disable </nowiki>
	\| xingoauth.properties:4		\| xingoauth.properties:4

Antje at 08:59, 8 July 2015

2015-07-08T08:59:03Z

← Older revision		Revision as of 08:59, 8 July 2015
Line 2,375:		Line 2,375:
	\| <nowiki>ENABLE_INTERNAL_USER_EDIT</nowiki>		\| <nowiki>ENABLE_INTERNAL_USER_EDIT</nowiki>
	\| <nowiki>TRUE</nowiki>		\| <nowiki>TRUE</nowiki>
	\| <nowiki>Define if users are allowed to edit their own contact object contained in folder 'Global Address Book' aka 'Internal Users'. ~~Switching this parameter only has an effect for new created contexts.~~ </nowiki>		\| <nowiki>Define if users are allowed to edit their own contact object contained in folder 'Global Address Book' aka 'Internal Users'. </nowiki>
	\| foldercache.properties:17		\| foldercache.properties:17
	\|-		\|-

Antje at 08:55, 8 July 2015

2015-07-08T08:55:47Z

← Older revision		Revision as of 08:55, 8 July 2015
Line 2,994:		Line 2,994:
	\| <nowiki>If the sum of all uploaded files in one request is larger than this value, the upload will be rejected. If this value is not set or 0, the more general MAX_UPLOAD_SIZE configured in server.properties will be used. If that value is also 0 or not set, uploads will be unrestricted. The size is in Bytes. </nowiki>		\| <nowiki>If the sum of all uploaded files in one request is larger than this value, the upload will be rejected. If this value is not set or 0, the more general MAX_UPLOAD_SIZE configured in server.properties will be used. If that value is also 0 or not set, uploads will be unrestricted. The size is in Bytes. </nowiki>
	\| infostore.properties:4		\| infostore.properties:4
			\|-
			\| <nowiki>com.openexchange.infostore.trash.retentionDays</nowiki>
			\| <nowiki>-1</nowiki>
			\| <nowiki> Specifies how many days items are kept in the trash folder until they are finally deleted. Cleanup is triggered during user login. A value equal to or smaller "0" disables automatic cleanup for items in the trash folder. The default value configured here takes effect on server granularity, but can be overwritten for sets of contexts, single contexts and single users. See http://oxpedia.org/wiki/index.php?title=ConfigCascade for more information.
			Depending on the "protected" flag of the corresponding preference path, users are able to change their configured value on their own. This can be adjusted via /meta/infostore.yml . Defaults to "-1". </nowiki>
			\| infostore.properties
	\|-		\|-
	\| <nowiki>com.openexchange.jolokia.servlet.name </nowiki>		\| <nowiki>com.openexchange.jolokia.servlet.name </nowiki>

Antje at 08:20, 8 July 2015

2015-07-08T08:20:54Z

← Older revision		Revision as of 08:20, 8 July 2015
Line 4,008:		Line 4,008:
	\| <nowiki>When searching for external participants in contact folders this option defines if contacts without email address are shown. </nowiki>		\| <nowiki>When searching for external participants in contact folders this option defines if contacts without email address are shown. </nowiki>
	\| participant.properties:7		\| participant.properties:7
	-		\|-
	\| <nowiki>com.openexchange.passwordchange.regexp</nowiki>		\| <nowiki>com.openexchange.passwordchange.regexp</nowiki>
	\| <nowiki>[^a-z0-9]</nowiki>		\| <nowiki>[^a-z0-9]</nowiki>

Antje at 08:16, 8 July 2015

2015-07-08T08:16:27Z

← Older revision		Revision as of 08:16, 8 July 2015
Line 4,008:		Line 4,008:
	\| <nowiki>When searching for external participants in contact folders this option defines if contacts without email address are shown. </nowiki>		\| <nowiki>When searching for external participants in contact folders this option defines if contacts without email address are shown. </nowiki>
	\| participant.properties:7		\| participant.properties:7
	\|-		-
	\| <nowiki>com.openexchange.passwordchange.regexp</nowiki>		\| <nowiki>com.openexchange.passwordchange.regexp</nowiki>
	\| <nowiki>[^a-z0-9]</nowiki>		\| <nowiki>[^a-z0-9]</nowiki>
	\| <nowiki>~~Defines~~ the ~~class of allowed special characters as Regular Expression~~. </nowiki>		\| <nowiki> Configures a regular expression pattern to use when calculating the strength if indicating "com.openexchange.passwordchange.showStrength" is "true", i.e. any character not matching the pattern increases the displayed password strength. Defaults to "[^a-z0-9]". </nowiki>
	\| passwordchange.properties:11		\| passwordchange.properties:11
	\|-		\|-
	\| <nowiki>com.openexchange.passwordchange.special</nowiki>		\| <nowiki>com.openexchange.passwordchange.special</nowiki>
	\| <nowiki>$, _, %</nowiki>		\| <nowiki>$, _, %</nowiki>
	\| <nowiki>~~Shows~~ an example of ~~allowed~~ special characters ~~to the user~~. ~~Should~~ be a subset of "regexp" ~~in a human readable format~~. </nowiki>		\| <nowiki>Defines a string that is shown as an example of special characters that increase a passwords' strength. This should be a subset of characters matched by the pattern defined at "com.openexchange.passwordchange.regexp".
			Defaults to "$, _, or %". </nowiki>
	\| passwordchange.properties:14		\| passwordchange.properties:14
	\|-		\|-
	\| <nowiki>com.openexchange.passwordchange.showStrength</nowiki>		\| <nowiki>com.openexchange.passwordchange.showStrength</nowiki>
	\| <nowiki>false</nowiki>		\| <nowiki>false</nowiki>
	\| <nowiki>~~Show~~ a ~~widget, which displays~~ the current ~~passwort Strength while entering~~. ~~Note:~~ The ~~UI algorithm looks for lower and upper case letters, numbers and special characters, but the overall~~ strength ~~depends~~ on the ~~length too~~. ~~For example a password with only 4 letters would be considered weak even if it meets several criteria~~.</nowiki>		\| <nowiki>Configures whether to show a graphical indicator reflecting the strength of the current password or not. The strength is evaluated based on matching performed against the pattern defined via "com.openexchange.passwordchange.regexp" during typing. Possible values are "true" to show the strength, or "false", otherwise. Defaults to "false". </nowiki>
	\| passwordchange.properties:2		\| passwordchange.properties:2
	\|-		\|-
	\| <nowiki>com.openexchange.passwordchange.minLength</nowiki>		\| <nowiki>com.openexchange.passwordchange.minLength</nowiki>
	\| <nowiki>4</nowiki>		\| <nowiki>4</nowiki>
	\| <nowiki>~~The~~ minimum length of an entered ~~password~~. </nowiki>		\| <nowiki>Specifies the minimum required length of a password entered by the user.
			Passwords shorter than the configured length are not accepted. Defaults to "4". </nowiki>
	\| passwordchange.properties:5		\| passwordchange.properties:5
	\|-		\|-
	\| <nowiki>com.openexchange.passwordchange.maxLength</nowiki>		\| <nowiki>com.openexchange.passwordchange.maxLength</nowiki>
	\| <nowiki>0</nowiki>		\| <nowiki>0</nowiki>
	\| <nowiki>The maximum length of an entered password. 0 for unlimited. </nowiki>		\| <nowiki>Specifies the minimum required length of a password entered by the user.
			Passwords shorter than the configured length are not accepted. A value of "0"
			disables the check and allows an unlimited length. Defaults to "0".The maximum length of an entered password. 0 for unlimited. </nowiki>
	\| passwordchange.properties:8		\| passwordchange.properties:8
			\|-
			\| <nowiki>com.openexchange.passwordchange.allowedPattern</nowiki>
			\| <nowiki></nowiki>
			\| <nowiki>Optionally configures a pattern to match the entered password against, i.e.
			only passwords matching this pattern will be accepted. Please note that the
			pattern is used to perform a 'positive' test against the entire entered
			password, and only matching strings are accepted, so use appropriate
			quantifiers as needed. For example, if the backslash character '\' should
			not be permitted in passwords, a pattern could look like "[^\\]*", or, if
			only ASCII characters should be allowed, the pattern "[\x00-\x7F]*" could
			be used (each without the quotation marks). By default, no pattern is
			configured, i.e. all character sequences are allowed.</nowiki>
			\| passwordchange.properties
			\|-
			\| <nowiki>com.openexchange.passwordchange.allowedPatternHint</nowiki>
			\| <nowiki></nowiki>
			\| <nowiki>Configures a string that is shown to users in an error message after trying
			to save a password not fulfilling the pattern defined in
			"com.openexchange.passwordchange.allowedPattern". This text should explain
			which characters are allowed according to the pattern, and is inserted for
			"[...]" in the following error message: "The entered password is illegal
			and can't be saved. Allowed characters are: [...]". Required if
			"com.openexchange.passwordchange.allowedPattern" is defined.</nowiki>
			\| passwordchange.properties
	\|-		\|-
	\| <nowiki>com.openexchange.capability.alone</nowiki>		\| <nowiki>com.openexchange.capability.alone</nowiki>

Antje at 07:39, 8 July 2015

2015-07-08T07:39:25Z

@@ Line 2,341: / Line 2,341: @@
 | <nowiki>Specifies the password used when creating the referenced keystore containing public-/private-key pair to use for encryption. Note that blank or null passwords are in violation of the PKCS #12 specifications. Required if &quot;com.openexchange.aws.s3.[filestoreID].encryption&quot; is set to &quot;rsa&quot;. </nowiki>
 | filestore-s3.properties:55
 |-
 | <nowiki>com.openexchange.find.basic.mail.searchmailbody </nowiki>

Antje at 14:10, 7 July 2015

2015-07-07T14:10:36Z

← Older revision		Revision as of 14:10, 7 July 2015
Line 1,979:		Line 1,979:
	\| <nowiki>com.openexchange.groupware.update.tasks.CheckForPresetMessageFormatInJSLob</nowiki>		\| <nowiki>com.openexchange.groupware.update.tasks.CheckForPresetMessageFormatInJSLob</nowiki>
	\| <nowiki>checks for possibly preset message format preference in JSLob and align the DB value accordingly</nowiki>		\| <nowiki>checks for possibly preset message format preference in JSLob and align the DB value accordingly</nowiki>
			\| <nowiki> </nowiki>
			\| excludedupdatetasks.properties
			\|-
			\| <nowiki>com.openexchange.groupware.update.tasks.DeleteFacebookContactSubscriptionRemnantsTask</nowiki>
			\| <nowiki></nowiki>
	\| <nowiki> </nowiki>		\| <nowiki> </nowiki>
	\| excludedupdatetasks.properties		\| excludedupdatetasks.properties