Is it possible to include binary data in an SAML Assertion token such that
the token is used to identify a SOAP client by inclusion of the token in the
SOAP Security Extension header i.e., <wss:security> element?
In the SAML spec it seems like there is a way to pass non-XML application
data that may be processed by a receiving party's security service?
It is possible to include binary data in SAML token as part of
and would conforming WSS SOAP Security implementation accept a SAML
token passed in the SOAP security header with binary token data included in
the Assertion token containing AttributeStatement in binary form?