#3084 Simplifying Web UI session timeout configuration
Closed: fixed 5 years ago Opened 5 years ago by edewata.

The session timeout for PKI Web UI can be configured with the <session-timeout> parameter in web.xml:

<session-config>
    <session-timeout>30</session-timeout>
</session-config>

However, there are multiple instances of web.xml within the server:

  • Global configuration: /etc/pki/<instance>/web.xml
  • PKI main webapp: /usr/share/pki/server/webapps/pki/WEB-INF/web.xml
  • PKI subsystem webapps: /usr/share/pki/<subsystem>/webapps/<subsystem>/WEB-INF/web.xml

Currently each of the above files defines its own <session-timeout> parameter. The parameters in the webapps will override the parameter in the global configuration but currently they are all set to the same value (i.e. 30 minutes).

The web.xml files in the webapps are actually shared files owned by PKI package which are not supposed to be modified, so to change the session timeout the admin would have to customize each webapp first, which requires a number of steps (see Customization), then modify the web.xml of the customized webapps. Also, once the webapps are customized, they will no longer be upgraded automatically in future PKI updates, so the admin would have to maintain them manually.

To simplify the process and avoid future issues, the <session-timeout> should be removed from the webapps, so by default PKI Web UI will use the global configuration which can be edited directly since it doesn't require customization and easily since it's only one file.


Metadata Update from @edewata:
- Issue assigned to edewata

5 years ago

Metadata Update from @edewata:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1658293
- Custom field type adjusted to None
- Custom field version adjusted to None

5 years ago

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Metadata Update from @edewata:
- Issue set to the milestone: 10.6.9

5 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/3201

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata