What messaging client implementation(s) and protocol(s) will your customer be using? What's their use-case?
Justin On Tue, Oct 31, 2023 at 2:34 PM SCOTT FIELDS <scott.fie...@kyndryl.com.invalid> wrote: > Only that our customer is migrating to cloud solutions and their desired > authentication/authorization service will be desired to use OIDC (OpenID > Connect). > > > > -----Original Message----- > From: Justin Bertram <jbert...@apache.org> > Sent: Tuesday, October 31, 2023 2:29 PM > To: users@activemq.apache.org > Subject: [EXTERNAL] Re: Native Oauth/OIDC integration in ActiveMQ > > As far as I'm aware, using JAAS *is* the "native" way to integrate with > security providers in both "Classic" and Artemis. I don't believe an Oauth > JAAS login module is being developed in the community. > > For what it's worth, most messaging protocols and/or clients don't support > Oauth anyway. > > Is there a specific use-case you have in mind that requires Oauth? > > > Justin > > On Tue, Oct 31, 2023 at 2:18 PM SCOTT FIELDS > <scott.fie...@kyndryl.com.invalid> > wrote: > > > To my knowledge, there is no native ActiveMQ integration for > > Authorization/Authentication via Oauth/OIDC. > > > > Is there any plan, if not, to include this, besides requiring an > > external JAAS method provided either by an external vendor or require > > a custom coding front-end from the end-use provider? > > > > If not, what's the best way to request this? > > > > Scott Fields > > Kyndryl > > Senior Lead SRE - BNSF > > 817-593-5038 (BNSF) > > scott.fie...@kyndryl.com<mailto:scott.fie...@kyndryl.com> > > scott.fie...@bnsf.com<mailto:scott.fie...@bnsf.com> > > > > >
