![]() ![]() Note that once a remember-me token is used for authentication, the token is invalidated and a new remember-me token is returned. Remember-me authentication is disabled completely.ĭefines the cookie name used for the remember-me authentication Remember-me cookie is only generated when checkbox is checked. No checkbox, remember-me cookie is always generated on successful login.Ĭheckbox is displayed on login form. ![]() The 'Remember my login' checkbox is only displayed when set to 'optional'. A short TTL, like the default, can reduce burst load on remote authentication systems (Crowd, LDAP) while keeping potential exposure to outdated credentials low, especially when paired with a shorter TTI.Ĭontrols whether remember-me authentication is disabled, always performed or only performed when a checkbox is checked on the login form. Longer TTLs pose a security risk, as potentially out-of-date credentials can still be used while they remain in the cache. The maximum allowed value is 300 seconds (5 minutes). Setting this to a value less than 1 will disable the cache. Setting this to a value less than 1 will default it to the configured TTL ( ).Ĭontrols the time-to-live for entries in the authentication cache. A short TTI (5 to 10 seconds) helps narrow the window for malicious users authenticating with outdated credentials and is recommended. count) is refreshed, defaults to 300 secondsĬontrols the time-to-idle for entries in the authentication cache. How frequently the retention file configuration cache (i.e. How long the distinct categories and actions cache is refreshed, defaults to 900 seconds How long the coverage cache is valid, defaults to 30 seconds Maximum number of audit events dispatched to consumer, defaults to 3,000 per batch Maximum number of audit events kept in buffer waiting to be consumed, defaults to 10,000 Maximum number of audit files, the earliest file will be deleted when limit is reached, defaults to 100 Size limit in megabytes for individual audit file, file rotates when limit is reached, defaults to 100MB Maximum number of audit events written to system log file in case of error, defaults to 3ĭatabase retention check, which deletes events exceeding retention period, running every day at midnight, and only runs if the last run is more than 23 hours. ĭatabase size check, running every 60 minutes Only allows the the system admin (but not admin) to see the global audit log Maximum number of events to be deleted per database transaction used when enforcing retention limits, defaults to 10,000 rows ![]() Maximum number of audit event rows stored in DB, events exceeding the limit get deleted in time order, defaults to 10M checked on hourly basisīuffer to accommodate new audit events, defaults to 1000 rows Timeout in seconds for a queued search request, defaults to 30 seconds Maximum number of concurrent freetext search requests allowed, defaults to 10 per node Maximum number of concurrent non-freetext search requests allowed, defaults to 10 per node If this property is set as true, those actions will be audited regardless of coverage settings. This property controls whether ADVANCED or FULL level logging is enforced for actions that were audited prior to application version 7.0.
0 Comments
Leave a Reply. |