Hi,
could you please elaborate the solution provided. Sample code of
some sort will help.
[I am grappling with the exact same problem, any solution with concrete
examples will be great help.]
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using
a
> > the webapplication call the "Issued-token" on the ADFS it can respond
> with
> > the already existing token?
> >
> >
> >
> > ----------
> > If you reply to this email, your message will be added to the discussion
> &g
e discussion
> below:
>
> http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5746057.html
> To unsubscribe from Issue with WS-Trust using security tokens/SAML
> assertions, click here
> <ht
SDL of
this STS instance.
You also need to set the property I mentioned previously to ensure that CXF
ignored the "ws-security.sts.client" configuration for the ADFS STS
communication (via WS-MEX).
Colm.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with
e issued
> token and the existing assertion in the STS.
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745487.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
h-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745487.html
Sent from the cxf-user mailing list archive at Nabble.com.
during the parsing of it
> I would say...?
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745474.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
-
215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745474.html
Sent from the cxf-user mailing list archive at Nabble.com.
tly then the first
> wsaws:Address should be the endpoint to the sts-webservice. The second
> wsaws:Address-element should be the address to the sts-metadata?
>
> The one thing I have missed may be a conduit. Is it neccessary to have a
> conduit for the adfs on the client?
>
uit. Is it neccessary to have a
conduit for the adfs on the client?
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745470.html
Sent from the cxf-user mailing list archive at Nabble.com.
I will try it out right away!
Testing is a good thing so feel free to use the ws-mex response.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745465.html
Sent from the cxf-user mailing list archive at
gt;
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745335.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
ry and a custom WSDLReader but I can't really
grasp where the inserts of the schemas should take place.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745335.html
Sent from the cxf-user mailing list archive at Nabble.com.
essage">
> element="t:RequestSecurityTokenResponse"/>
>
> *
>
> *
>
> element="trust:RequestSecurityTokenResponseCollection"/>
>
>
> When I debug the "schema" named
> "
> http://schemas.microsoft.com/ws/2
s-trust/200512"/>
*
*
When I debug the "schema" named
"http://schemas.microsoft.com/ws/2008/06/identity/securitytokenservice/Imports";
is found but contains nothing.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-sec
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745190.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
ext:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745190.html
Sent from the cxf-user mailing list archive at Nabble.com.
gt;
>
>
>
> If we look at the line where everything fails it's line 272 in
> PhaseInterceptorChain.java
> That lines say: currentInterceptor.handleMessage(message);
> This all happens inside a while-loop:
>
> while (state == State.EXECUTING &
n tell.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5744967.html
Sent from the cxf-user mailing list archive at Nabble.com.
Good point I didn't think of that at all. No I used the snapshot version from
the maven-repository. Will build it myself and try again.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5744865.html
Sent
too much?
>
>
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5744744.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
-ws-addr.
Maybe we are importing a bit too much?
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5744744.html
Sent from the cxf-user mailing list archive at Nabble.com.
bit faulty I
> believe.
>
> The error is "sp:KeyValueToken/wsp:Policy must have a value".
>
> Is this the actual error or are there still some configuration missing? Can
> this parsing-error be "fixed" by cxf?
>
>
>
> --
> View this message in
lieve.
The error is "sp:KeyValueToken/wsp:Policy must have a value".
Is this the actual error or are there still some configuration missing? Can
this parsing-error be "fixed" by cxf?
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Tru
elG <
michael.gustafs...@migrationsverket.se> wrote:
> We have done that earlier, but now it´s just the "issued token" in the WSDL
> that starts up the sts client.
>
> /Mike
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.c
We have done that earlier, but now it´s just the "issued token" in the WSDL
that starts up the sts client.
/Mike
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5744624.html
Sent from the cxf-us
>
>
>
>
>
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5744462.html
Sent from the cxf-user mailing list archive at Nabble.com.
-Trust-using-security-tokens-SAML-assertions-tp5744142p5744460.html
Sent from the cxf-user mailing list archive at Nabble.com.
at
>
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
> at
>
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
> at
>
> org.apache.tomcat.util.net.JIoEndpoint$Socke
)
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5744385.html
Sent from the cxf-user mailing list archive at Nabble.com.
but probably not). Anyway the sts client later
> on complains about the soap version mismatch and the message is not yet
> sent
> to the STS.
>
> So actually one step back and two step forward :)
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabb
abble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5744364.html
Sent from the cxf-user mailing list archive at Nabble.com.
tp://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5744317.html
Sent from the cxf-user mailing list archive at Nabble.com.
f the box") making the endpoint address of the STS is a
> problem? Should´nt we at least see a connection attempt or endpoint address
> error message?
>
> Should the Shibboleth SP in some way be invoked to request the token?
>
> Why the loop?
>
> A lot of questions but no so
On May 19, 2014, at 4:04 AM, MichaelG
wrote:
> The scenario:
>
> Idp/STS: Microsoft ADFS 2.0
> Service provider: Shibboleth SP
> CXF: 2.7.8
>
> The client logs on (with a domain username/pwd) to the web site. Once logged
> on the user can call a webservice that is WS-trust configured.
>
>
//cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142.html
Sent from the cxf-user mailing list archive at Nabble.com.
37 matches
Mail list logo
