Info: Performing the steps described in this article requires direct server access. Depending upon how your system is hosted and the level of access you have to that system, coordination may be required with your Partner or WoodWing Support team. For a full overview of the steps that need to be done by WoodWing and how to request them, see WoodWing Cloud - Change management.
The time after which a logon automatically expires when no activity was detected can be controlled by the options described below.
Note: The setting can be defined to be different for Web clients because these are typically not logged off (browser users often close a window without logging off, which leaves them logged into the system).
Generic logon expiration
- File: configserver.php file (recommended: config_overrule.php file)
- Name of option: EXPIREDEFAULT
- Values:
- Minimum value: 900 (in seconds)
- Default setting: 24 hours (defined as 24 x 3600)
- Example:
define ('EXPIREDEFAULT', 24*3600);
Expiration for Web-based clients
Note: This setting can be used for all Web-based clients except Studio, for which the EXPIREDEFAULT setting should be used (above).
- File: configserver.php file (recommended: config_overrule.php file)
- Name of option: EXPIREWEB
- Value:
- Minimum value: 900 (in seconds)
- Default setting: 1 hour (defined as 3600 seconds)
- Example:
define ('EXPIREWEB', 3600);
Comment
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
0 comments
Please sign in to leave a comment.