Re: Unable to see SOAP headers while using UsernameToken assertion

I forgot to mention that I am setting ws-security.username and ws-security.password programmatically onto BindingProvider. Thanks, Giriraj On Feb 24, 2016 11:07 PM, "Giriraj Bhojak" wrote: > Hi, > > I have been trying to use UsernameToken WS-SecurityPolicy assertion, but I

Unable to see SOAP headers while using UsernameToken assertion

Hi, I have been trying to use UsernameToken WS-SecurityPolicy assertion, but I do not see the SOAP headers in the payload. Hence I keep getting the following exception on the server side: org.apache.cxf.ws.policy.PolicyException: These policy alternatives can not be satisfied:

Re: JAX-RS CookieHeaderProvider with httpOnly cookie doesn't work

Hi Yes, you send a NewCookie but attempt to read it later on as Cookie. You should use NewCookie.valueOf(newCookieValue) to recreate it. Can you please use one of Cookie constructors to convert NewCookie to Cookie ? Or simply take the relevant value from this new cookie and send the name

Re: No support for FailoverFeature in CXF Rest Client implementation (version 3.1.0)

Hi Please create a CXF JIRA issue, not sure how to qualify it, 'Task' I guess. As I said though it is unlikely to be addressed in the short term unless one of colleagues or yourself will look at it. Cheers, Sergey On 24/02/16 16:36, ranadeep.sha...@gmail.com wrote: Hi Sergey, Thanks for

Re: JAX-RS CookieHeaderProvider with httpOnly cookie doesn't work

Sorry, now I understand your question.. please find,I think, the bad code that I use to create a new webclient to make the request : Thanks for your time -- View this message in context:

Re: No support for FailoverFeature in CXF Rest Client implementation (version 3.1.0)

Hi Sergey, Thanks for the reply. Is there any place where I can raise a request for this feature implementation ? That way, I believe all CXF consumers including myself can keep a track of it. Regards, Ranadeep. -- View this message in context:

Re: Proxy-based API genaration (two or more interaces)

Hi On 24/02/16 13:42, Vjacheslav V. Borisov wrote: Hi! Currently it is possible to write server side resource implementing two interfaces at the same time Eg,. public class SomeResource implements OneResourceInterface, TwoResourceInterface does it possible to generate Proxy-based client

Proxy-based API genaration (two or more interaces)

Hi! Currently it is possible to write server side resource implementing two interfaces at the same time Eg,. public class SomeResource implements OneResourceInterface, TwoResourceInterface does it possible to generate Proxy-based client based on more that one interface?

Re: [cxf-fediz] advanced IDP federation of multiple realms possible?

Hi Ingo, I think it should be feasible to get this scenario working in Fediz. However, the only way I can see it working is if the IDP-A at least knows to send requests for REALM-C to IDP-B for validation, passing through the home realm. Actually I just reviewed the code, and the WS-Federation

Re: No support for FailoverFeature in CXF Rest Client implementation (version 3.1.0)

Hi Ranadeep, On 24/02/16 01:35, ranadeep.sha...@gmail.com wrote: Hi Sergey, Thanks for the response. We have a requirement where we are planning to preserve the usage of standard API going forward so that the functionality is not impacted, no matter what the underlying implementation is. I

Re: NullPointerException in OAuthRequestFilter

Hi Thanks for being so appreciative, but I'm only trying to provide whatever info I can, we work with all the users this way :-) I honestly do not know where are you getting these dependencies from. And if you wish to run your application in Glassfish you do not have to start going the