|
|
|
|
|
In addition to the options shown below, Connect Daily supports authentication of Users via LDAP or Active Directory. For information on this refer to Authentication Architecture.
Setting this option will cause Connect Daily to give rights to all created Objects to all existing Groups.
New Users will be made members of all Groups.
This is the User name that should be supplied when a User requests a Calendar View while not logged in. This User name will be supplied to the security sub-system to determine what Calendars, Groups, Resources, etc. the User can see. See also: Permissions for Anonymous Users (Permissions for Anonymous Users, User Preferences)
Setting this option will allow Users to set cookies with their User ID and Password. The down side of enabling this feature is that anyone who can access the browser profile will be able to login. This option only works when using the non-default plain text authenticator.
Setting this to Yes prevents Users from changing their password. Mainly used for demonstration mode.
The default User name and password for the login screen. This is really an option for demonstration purposes. In a production system, you should disable it by removing the values.
If you are using an authentication provider that supports automatically creating users (Container and LDAP authentication) this is the user account to copy user preferences and default security configuration from. See Automatically Creating Users for additional information.
By default, Connect Daily does not allow you to enter JavaScript as part of an Item description. This is to make cross-site scripting attacks more difficult, and make Connect Daily safer for Users. If you wish, you can set this option to Yes to allow operators to enter JavaScript as part of an Event description. You should not set this option if you allow the public to add Events.
User passwords must have at least one alpha, one digit, and non-digit non-alpha character.
The number of characters a password must contain. Default is 5.
If N bad login attempts occur, then the account is locked for a specified period or until the administrator unlocks the account.
The number of minutes to lock an account after bad login attempts happen. Setting this to a negative number means forever and an administrator will have to re-enable the account.
When a User's password expires, this is how many logins they can perform until their account is locked.
The number of minutes the account should be locked after a bad login attempt. If this number is negative, then the enabled flag on the account is cleared and it will require an administrator to re-enable the account.
Set this value to the number of days you want Users to be able to keep the same password. Set this to -1 to not require periodic password changes.
If this value is set, and non-zero, then at least this many days must elapse before the User will be allowed to change their password.
If this value is non-zero, then N passwords will be retained for comparison to any new User password. If the new password has been used before, the password change attempt will fail.