cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From coheigea <>
Subject Re: Issue with WS-Trust using security tokens/SAML assertions
Date Mon, 07 Jul 2014 09:00:08 GMT
Sorry, I don't follow you. Could you outline how you expect the token flow
to work in detail? From my POV, if the STS requires an IssuedToken, the
client must obtain this token from another STS instance.


On Mon, Jul 7, 2014 at 7:47 AM, roband915 [via CXF] <> wrote:

> The Shibboleth SP that we're using actually communicates with the same STS
> as the webapplication should do. So there is only one STS.
> When my Shibboleth SP recieves the token from the ADFS, Isn't the ADFS
> then "aware" that there is a valid token sent to this client? So when I via
> 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
> below:
>  To unsubscribe from Issue with WS-Trust using security tokens/SAML
> assertions, click here
> <>
> .
> <>

Colm O hEigeartaigh

Talend Community Coder

View this message in context:
Sent from the cxf-user mailing list archive at

View raw message