[
https://issues.apache.org/jira/browse/ARTEMIS-6037?focusedWorklogId=1018025&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1018025
]
ASF GitHub Bot logged work on ARTEMIS-6037:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Apr/26 01:22
Start Date: 30/Apr/26 01:22
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #6396:
URL: https://github.com/apache/artemis/pull/6396#issuecomment-4348862079
I dealt with the test failures and also made some changes in
`org.apache.activemq.artemis.core.server.cluster`, added a couple tests for
those changes, and ran the test-suite again which looks good.
Issue Time Tracking
-------------------
Worklog Id: (was: 1018025)
Time Spent: 40m (was: 0.5h)
> Refactor handling of cluster credentials
> ----------------------------------------
>
> Key: ARTEMIS-6037
> URL: https://issues.apache.org/jira/browse/ARTEMIS-6037
> Project: Artemis
> Issue Type: Task
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> To strengthen broker security out-of-the-box we should reject any connection
> using the default cluster credentials. We already force users to explicitly
> select a custom username and password when a non-clustered broker instance is
> created. Additionally, we force them to explicitly select custom cluster
> credentials when creating a clustered broker instance. However, there are
> still default values for cluster credentials that we should categorically
> reject.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
