: Including BinarySecurityToken in the SOAP header

[Brent Putman]

On 3/28/12 9:22 PM, Gina Choi wrote:
> 
> 
> I try to use X.509 Token Profile
> 1.1(http://www.oasis-open.org/committees/download.php/16785/wss-v1.1-spec-os-
> x509TokenProfile.pdf
> ) of the ws 1.3 specification to authenticate client.


That's fine, but that token profile is just specifying how to represent
the X.509 cert as a token in the Security header.  It doesn't really say
anything about how the signature is being done, over what elements, etc,
which is what you really need to know.


> My ADFS has a
> corresponding end point which is
> https://strts01.ams.dev/adfs/services/trust/13/certificate. Do you have a
> test case similar to this to look at? At the moment, I am interested in
> Reference to a Binary Security Token(Line 318 - 363 in the profile).


No, don't have much in the way of WS-* code examples at all.  Most of
our code there was contributed by others.  Our team has never really
implemented much using the WS-* schemas.

What you really need to ask somewhere is: what does the ADFS STS expect
or support in the way of WS-Security and WS-Trust usage?