[
https://issues.apache.org/jira/browse/ARTEMIS-4709?focusedWorklogId=912878&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-912878
]
ASF GitHub Bot logged work on ARTEMIS-4709:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Apr/24 17:13
Start Date: 03/Apr/24 17:13
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4871:
URL:
https://github.com/apache/activemq-artemis/pull/4871#issuecomment-2035146948
Is there a particular reason this needs to be a plugin vs. just a normal bit
of functionality in the core server? Plugins are nice for some things, but
they're kind of clunky to configure. This seems like something that would fit
well on an `acceptor` URL.
Issue Time Tracking
-------------------
Worklog Id: (was: 912878)
Time Spent: 1h 10m (was: 1h)
> 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: 1h 10m
> 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)
