[ 
https://issues.apache.org/jira/browse/ARTEMIS-4149?focusedWorklogId=842354&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-842354
 ]

ASF GitHub Bot logged work on ARTEMIS-4149:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Jan/23 17:53
            Start Date: 30/Jan/23 17:53
    Worklog Time Spent: 10m 
      Work Description: gtully opened a new pull request, #4350:
URL: https://github.com/apache/activemq-artemis/pull/4350

   …te to jass reloadable properties status in the absence of login attempts




Issue Time Tracking
-------------------

            Worklog Id:     (was: 842354)
    Remaining Estimate: 0h
            Time Spent: 10m

> add watcher to login.config dir to trigger jass property reload
> ---------------------------------------------------------------
>
>                 Key: ARTEMIS-4149
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4149
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Configuration, JAAS
>    Affects Versions: 2.27.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>             Fix For: 2.28.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The contents and modification of jaas re-loadable properties are visible in 
> the status, however they are reloaded on next use, which requires a jaas 
> login attempt. For some login modules this may never never be triggered.
> By adding the login.config to the watch list, modifications to that directory 
> can trigger a reload and status update based on the 
> configurationFileRefreshPeriod cycle.
> This ensures that the status flied can be reliably updated.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to