認識済みのシステム プロパティ
Crowd supports some configuration and debugging settings that can be enabled through Java system properties. System properties are usually set by passing the -D
flag to the Java virtual machine in which Crowd is running. For full instructions, refer to Configuring system properties.
Property Name | 説明 | 利用可能バージョン | 既定値 |
---|---|---|---|
| When set to This header can be used in Tomcat's access logs. | 4.0.3 | true |
| When set to This header can be used in Tomcat's access logs. | 4.0.3 | true |
| For the XML membership REST endpoint (like outgoing membership), this property defines whether the optimized version of synchronization should be used. According to manual tests of an application with 1 M users in four directories, enabling this feature saves ~2 hours for full synchronisation of memberships and increases memory consumption by ~300 MB. | 4.1.2 | true |
| For the internal full synchronisation process (from Active Directory to Crowd database tables), this property defines whether membership details should be retrieved upfront. With the legacy approach, memberships are retrieved for each group individually (for both group and user-based directories). For an Active Directory instance with many groups and users, the full synchronisation can take several hours or more. The preferred (non-legacy) approach is to retrieve all membership details as part of an upfront request to Active Directory. With this approach, the full synchronisation can be completed in several minutes (depending on the server, database, and the speed and specifications of an Active Directory). Normally, the non-legacy approach should not use much (if any) additional memory (when compared to the legacy approach). Refer to | 5.3.0 | false |
| This property defines whether the mapper configuration is used when checking This check has been discovered to make a surplus call to Set this property to | 5.3.6 | true |
| This property controls how incremental synchronization works for an Active Directory. The incremental synchronization of users has two flavors:
| 5.3.0 | false |
| This property disables the caching performed by In general, the This property addresses the situations when a customer is having a problem with sync processing and has turned on legacy mode ( In such a case, this flag can be used (in addition to the legacy property | 5.3.0 | false |
| When set to | 4.4.0 | true |
| When set to an integer, Crowd web application’s | 4.1.10 | 10 |
| Since 4.4, Crowd does not allow external apps to change user emails. Enabling this property bypasses this rule—if this property is set to Do not enable this property when using Crowd as an SSO provider, because it will cause a security vulnerability in applications that use email as a UID (unique identifier). | 4.4.0 | false |
| Enables swallowing exceptions and returning empty results in the directory search methods. | 4.4.0 | false |
| Sets the cache size of the | 5.0.4 | 1000 |
| Enables request batching to verify if a user or group is a direct member of a parent group. The batching of requests happens during incremental synchronisation when determining recreated memberships. | 5.0.4 | true |
| When set to true, this property enables escaping the underscore ( | 5.1.2 | true |
| Enables a filter that suppresses log messages containing "no data" from HSQL (HyperSQL) database operations. | 5.2.0 | true |
| Enables Crowd’s advanced PBKDF2-HMAC-SHA512 password encoder with 210,000 iterations. | 5.2.1 | false |
| Controls whether security annotations are applied to Struts actions, servlets, and filters. | 6.0.0 | true |
| Controls whether security annotations are applied to plugin actions, servlets, and filters. | 6.0.0 | true |
| Determines whether the caching of By default, it’s set to | 6.0.0 | true |
| Determines whether licensed access is enabled by default, in cases when there is no annotation. | 6.0.0 | true |
| When set to true, the legacy This can be useful for backward compatibility or specific use cases where the default constraints are not preferred. | 6.2.3 | false |
| Enables deduplication of users returned by Azure. | 5.3.7 | true |