the case :)
Sorry for the noise! :)
BR,
- Simon
From: Matt Pavlovich
Sent: 16 April 2024 15:45:25
To: users@activemq.apache.org
Subject: Re: ActiveMQ Classic v6.x - Encrypted passwords for web-based services
Hi Simon-
JAAS provides this and ActiveMQ servi
:09
> To: users@activemq.apache.org
> Subject: Re: ActiveMQ Classic v6.x - Encrypted passwords for web-based
> services
>
> Note — This also falls under one of the goals for ActiveMQ 7.x’s non-Spring
> bootstrapping to support single JAAS-provider for all services, that uses
>
From: Matt Pavlovich
Sent: 16 April 2024 05:06:09
To: users@activemq.apache.org
Subject: Re: ActiveMQ Classic v6.x - Encrypted passwords for web-based services
Note — This also falls under one of the goals for ActiveMQ 7.x’s non-Spring
bootstrapping to support single JAAS-provider for
Note — This also falls under one of the goals for ActiveMQ 7.x’s non-Spring
bootstrapping to support single JAAS-provider for all services, that uses
broker-wide crypto and config services to handle encrypted macro expansion
across authn/authz and config params.
> On Apr 13, 2024, at 11:49 PM,
Hi Martin
That's normal: broker authentication and webconsole/api authentication
are two different layers (it's intentional).
If, in theory, it would be possible to configure conf/jetty.xml to use
the same authentication files as for broker, Jetty doesn't use exactly
the same authentication schema
