Hi Andriy, Yes, kind of. The service must proceed parallel requests from different clients having own security requirements: - activated/deactivated JWT authentication - JWS - JWE - authorization
The security requirements are controlled dynamically through the central repository and are obtained on runtime by client and services. It will be useful for such use case to control filters chain dynamically per request base, in the same way as SOAP interceptors. Regards, Andrei. > -----Original Message----- > From: Andriy Redko [mailto:drr...@gmail.com] > Sent: Mittwoch, 3. April 2019 23:28 > To: Andrei Shakirin; dev@cxf.apache.org > Subject: Re: Dynamic JAX-RS filters (per request/response) > > Hi Andrei, > > I would be curious to understand a bit regarding the use case(s). Is it going > to > be driven by presence of some headers fe? Or something else? Like f.e. each > message is inspected, and depending on some criteria, the different filter > chains are being constructed? Could you share a couple of examples? > > Thank you. > > Best Regards, > Andriy Redko > > AS> Hi, > > AS> Currently JAX-RS filters are bound to exchange endpoint in > AS> ClientProviderFactory and ServerProviderFactory and filter chain is always > the same for all processing messages. > AS> In some use cases (security) it would be useful to activate filters > dynamically on message level, that different requests could have own filter > chains. > > AS> I am going to extend JAXRSInInterceptor, JAXRSOutInterceptor, > AS> ClientRequestFilterInterceptor and ClientResponseFilterInterceptor with > option to add and execute filters dynamically, additionally to > ClientProviderFactory and ServerProviderFactory. > > AS> Any objections, thoughts regarding that? > > AS> Regards, > AS> Andrei. > AS> As a recipient of an email from Talend, your contact personal data > AS> will be on our systems. Please see our contacts privacy notice at > AS> Talend, Inc. <https://www.talend.com/contacts-privacy-policy/> > >
