[jira] [Work logged] (AMQ-8391) Consolidate to a single JAAS for jmx, messaging and web layers

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot logged work on AMQ-8391:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Oct/23 11:33
            Start Date: 03/Oct/23 11:33
    Worklog Time Spent: 10m 
      Work Description: cshannon commented on PR #1057:
URL: https://github.com/apache/activemq/pull/1057#issuecomment-1744776838

   Can this wait until 6.1.0? The issue has been open for a while and doesn't seem like it would be a big deal if it was done in 6.1.0
   
   I took a quick look but i am not familiar with any of the stuff here and i would need more time than i have this week likely to look into it if you need help fixing it and i know we were trying to get 6.0.0 out soon




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

    Worklog Id:     (was: 883077)
    Time Spent: 0.5h  (was: 20m)

> Consolidate to a single JAAS for jmx, messaging and web layers
> --------------------------------------------------------------
>
>                 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: 0.5h
>  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)