AW: How to get username of authenticated user to create a token for a downstream call

Hi Colm I tried this, but the SecurityContext is always null. I am surely missing something. My web service is configured with the WSS username/password validator: endpoint.getInInterceptors().add(wss4JInInterceptor);

Re: How to get username of authenticated user to create a token for a downstream call

Yes trying to retrieve the SecurityContext from the Message in a separate interceptor chain won't work. You could try adding an interceptor on the receiving side to store the Security Context principal so that it's accessible to your client somehow. I'm not sure if storing it on the message

Re: SRP authentication

Hi, There isn't any support in CXF for SRP using WS-Policy or otherwise, as far as I'm aware. Do you have a link to some documentation about how SRP would work with SOAP messages? Colm. On Wed, Sep 12, 2018 at 12:43 PM Jens wrote: > Hi list, > > does CXF include support for authentication via

Re: SRP authentication

Hi Colm, at the moment I only have (confidential) high-level documentation that basically says - use the AWS SDK to make an authentication request (-> ID token and access token) - add the ID token as an HTTP header to the SOAP request - add the ID token and the access token as SOAP headers to

Re: ContainerRequestContext.getHeaders() Returns Concatenated Values?

I created two JIRAs: https://jira.apache.org/jira/browse/CXF-7842 https://jira.apache.org/jira/browse/CXF-7843 I listed them both as bugs, but we may want to change 7843 to an "improvement" or something maybe? I don't know. I am working on 7842 now. On Thu, Sep 13, 2018 at 3:41 PM Andy

Re: ContainerRequestContext.getHeaders() Returns Concatenated Values?

Yeah, no problem. You mind if I take a stab at the PR? On Thu, Sep 13, 2018 at 2:20 PM Andy McCright wrote: > So it sounds like there are two issues here: > > 1) The "org.apache.cxf.http.header.split" property is applied > inconsistently - it works correctly in HttpHeaders, but not in >

Re: ContainerRequestContext.getHeaders() Returns Concatenated Values?

Andy, I've submitted a PR for the splitting part (not the changing the defaults): https://github.com/apache/cxf/pull/445 There was some funky stuff going on in there with how it nulls out the existing HttpHeaders object on the ContainerRequestContextImpl. I wasn't quite sure why that was being

Re: ContainerRequestContext.getHeaders() Returns Concatenated Values?

By all means! :) Let me know once you've got something ready for review. Thanks! On Thu, Sep 13, 2018 at 2:31 PM James Carman wrote: > Yeah, no problem. You mind if I take a stab at the PR? > > On Thu, Sep 13, 2018 at 2:20 PM Andy McCright > > wrote: > > > So it sounds like there are two

Re: ContainerRequestContext.getHeaders() Returns Concatenated Values?

I also created a branch of my project which uses the local version of CXF 3.3.0-SNAPSHOT with my changes in it. I am able to use ContainerRequestContext and I no longer have to set the property! W00T! https://github.com/jaxxy-rs/jaxxy/tree/cxf-3.3.0-snapshot Thanks for taking the time to help,

Re: ContainerRequestContext.getHeaders() Returns Concatenated Values?

So it sounds like there are two issues here: 1) The "org.apache.cxf.http.header.split" property is applied inconsistently - it works correctly in HttpHeaders, but not in ContainerRequestContext.getHeaders(). This seems like a bug to me. 2) The value for this property should be true by default -