rch 23, 2016 7:47 AM
To: cohei...@apache.org<mailto:cohei...@apache.org>
Cc: users@cxf.apache.org<mailto:users@cxf.apache.org>
Subject: RE: STSClient.validateSecurityToken expects
RequestSecurityTokenResponseCollection?
I was used to using the interceptors from other projects, so I di
pell, Stephen CTR (FAA)
> Sent: Wednesday, March 23, 2016 7:47 AM
> To: cohei...@apache.org
> Cc: users@cxf.apache.org
> Subject: RE: STSClient.validateSecurityToken expects
> RequestSecurityTokenResponseCollection?
>
> I was used to using the interceptors from other projects,
e.org
Cc: users@cxf.apache.org
Subject: RE: STSClient.validateSecurityToken expects
RequestSecurityTokenResponseCollection?
I was used to using the interceptors from other projects, so I didn’t really
give it any thought; but it does make more sense to use the policy approach.
Now if I can
: Wednesday, March 23, 2016 7:40 AM
To: Chappell, Stephen CTR (FAA)
Cc: users@cxf.apache.org
Subject: Re: STSClient.validateSecurityToken expects
RequestSecurityTokenResponseCollection?
I guess so. It's unusual to use the WSS4J interceptors when invoking on the
STS, all of the testing is done
Stephen W. Chappell
>
>
>
> -Original Message-
> From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
> Sent: Wednesday, March 23, 2016 7:27 AM
> To: users@cxf.apache.org
> Subject: Re: STSClient.validateSecurityToken expects
> RequestSecurityTokenResponseCo
ing the right properties in the property map to make
it all work. Am I on the right track with that?
Thanx,
Stephen W. Chappell
-Original Message-
From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
Sent: Wednesday, March 23, 2016 7:27 AM
To: users@cxf.apache.org
Subject: Re: STSClient.valid
What does your WSDL look like? At a guess it is expecting the Collection to
be returned as opposed to the single element. The portType should look
something like:
http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Validate;
message="tns:RequestSecurityTokenMsg"/>
