[
https://issues.apache.org/jira/browse/ARTEMIS-4709?focusedWorklogId=914814&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914814
]
ASF GitHub Bot logged work on ARTEMIS-4709:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Apr/24 09:05
Start Date: 16/Apr/24 09:05
Worklog Time Spent: 10m
Work Description: gtully commented on PR #4871:
URL:
https://github.com/apache/activemq-artemis/pull/4871#issuecomment-2058602117
on the config change, if a similar feature became available in the core, it
would never be a breaking change, it would require a config change, but not a
break. new config would be needed and the plugin removed.
But more generally, on plugins for "users", I think it is an extension
point, but we are all users!
Issue Time Tracking
-------------------
Worklog Id: (was: 914814)
Time Spent: 2h (was: 1h 50m)
> Add a plugin to provide periodic expiry of connections on a per acceptor basis
> ------------------------------------------------------------------------------
>
> Key: ARTEMIS-4709
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4709
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 2.33.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.34.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> When credential rotation needs to be enforced, active connections need to be
> terminated on some timeline to ensure credentials are reevaluated. There are
> management apis that can be used but these require some intervention.
> In addition to enforce some SLA around duration of connections, having an
> easy way to limit connections to a given maximum period can be helpful.
> A plugin that will be applied on an per acceptor basis, that can be used to
> disconnect connections that have lived for some period can provide a nice
> building block for these use cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
