When I upgraded from 3.0.4 to 3.1.3 not having message.setContextualProperty
broke my Kerberos authentication.
In case the wsdl is under Kerberos security, I setup a ConduitConfigurer which
has a Kerberos AuthSupplier.
This AuthSupplier needs to set "auth.spnego.useKerberosOid" to "true"
As a workaround I'm using reflection as follows:
Method m = MessageImpl.class.getDeclaredMethod ("setContextualProperty",
String.class, Object.class);
m.setAccessible (true);
m.invoke (message, new Object [] {"auth.spnego.useKerberosOid", "true"});
Is there a better way to do this ?
Thanks,
Roger
-----Original Message-----
From: Daniel Kulp [mailto:[email protected]]
Sent: Sunday, November 15, 2015 6:40 PM
To: [email protected]
Subject: Re: Equivalent of Message.setContextProperty
Just a message.put(…)
Anything that was set with message.setContextualProperty could potentially be
lost the next time contextual properties were calculated. It was only supposed
to be called by the routines that collect the various properties and if those
routines were called again, the contextual map is cleared. It was never meant
to be public.
Dan
> On Nov 15, 2015, at 12:56 PM, John D. Ament <[email protected]> wrote:
> I'm upgrading an app to be based on CXF 3.1 (from 3.0.5). In 3.0.5, I
> could do
>
> message.setContextualProperty(SecurityConstants.USERNAME_TOKEN_VALIDAT
> OR,tokenValidator);
>
> from within an AbstractPhaseInterceptor. This method no longer
> exists. Is there an equivalent?
>
> John
--
Daniel Kulp
[email protected] - http://dankulp.com/blog Talend Community Coder -
http://coders.talend.com
This email (including any attachments) may contain information which is
privileged, confidential, or protected. If you are not the intended recipient,
note that any disclosure, copying, distribution, or use of the contents of this
message and attached files is prohibited. If you have received this email in
error, please notify the sender and delete this email and any attached files.
