Feature: configurable backend session timeout
Open
@dsolistorres is already working on this.
Since Dec 30, 2025.
dotCMS : Security
OKR : Core Features
OKR : Security & Privacy
Priority : 3 Average
Team : Maintenance
Team : Security
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
https://dotcms.freshdesk.com/a/tickets/34590
Summary
- Backend session timeout currently fixed, unlike front-end keep-alive options.
- Security team requests ability for customers to tune timeout values per environment.
- Implement configurable backend session timeout exposed via standard configuration property.
Context
Slack request from security channel (Mehdi Karimi) noted that only front-end keep alive exists today (https://dev.dotcms.com/docs/request-response-and-session#SessionKeepAlive). Customers using the OWASP plugin cannot adjust backend session expiry in core and need native support to align with their policies.
Acceptance Criteria
- Add configuration property (e.g.,
SESSION_TIMEOUT_MINUTES) with sensible default matching current behavior. - Document how admins can set the value (docs + release notes).
- Ensure timeout propagates through backend session management (login, admin UI, REST).
- Include automated tests covering default and custom values.
Additional Notes
- Coordinate with security reviewers to validate defaults.
- Consider backward compatibility for existing installations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.