You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2023/10/20 21:11:00 UTC

[jira] [Updated] (AMQ-8391) Migrate jetty to use shared JAAS realm with messaging

     [ https://issues.apache.org/jira/browse/AMQ-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Pavlovich updated AMQ-8391:
--------------------------------
    Summary: Migrate jetty to use shared JAAS realm with messaging  (was: Consolidate JAAS for messaging and web layers)

> 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: 3h
>  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)