[
https://issues.apache.org/jira/browse/AMQ-8391?focusedWorklogId=888084&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-888084
]
ASF GitHub Bot logged work on AMQ-8391:
---------------------------------------
Author: ASF GitHub Bot
Created on: 31/Oct/23 13:29
Start Date: 31/Oct/23 13:29
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #1100:
URL: https://github.com/apache/activemq/pull/1100#issuecomment-1787222306
At first glance, it looks good. I'm doing some tests to validate.
Issue Time Tracking
-------------------
Worklog Id: (was: 888084)
Time Spent: 4h (was: 3h 50m)
> Migrate jetty to use shared JAAS realm with messaging
> -----------------------------------------------------
>
> Key: AMQ-8391
> URL: https://issues.apache.org/jira/browse/AMQ-8391
> Project: ActiveMQ
> Issue Type: Task
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Fix For: 6.0.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> Currently, the default Apache ActiveMQ distribution has 3 user and group
> backends-- jmx, messaging and web.
> Update:
> 1. Migrate the jetty.xml to use the JAAS backend used for messaging
> 2. Add the jaasAuthentication to default activemq.xml (so it is explicitly
> visible)
> 3. Update the web-console servlet to permite access via 'web-console-role'
> 4. Update the api servlet to allow access using 'rest-role'
> 5. Add admin to the 'web-console-role' and 'rest-role' by default
> 6. Migrate jmx to use the 'activemq' realm
> 7. Create default jmx-readwrite-role and jmx-readonly-role roles in the
> conf/jmx.access file
> 8. Include the config breaking change in release notes
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
