Constraining the choice of BSP token profile

[ri...@us.ibm.com]

In the early days of developing the Basic B2B Profile, we considered
whether or not to constrain the choice of BSP token profiles which can
be used while conforming to the Basic B2B Profile. If I recall
correctly, I think the thought was that since not all platforms will
support all the same token profiles, it might help interoperability if
we constrained the choice to only the most commonly supported token
profiles.

I wanted to know what people thought. Is the lack of uniform support
for BSP token profiles likely to be the source of interoperability
problems? If so, does constraining the choice seem like a reasonable
way to help improve the likelihood of interoperable Web services? Of
course, if constraining the choice of token profiles seems like it will
improve interoperability, the next question is which token profiles to
restrict?

Thanks,

Rimas

[Anthony Nadalin]

Since the BSP has allowed conformance to the base, one can use any token and still claim conformance, this will sure cause interoperability issues. I believe is you constrain to the token profiles that the BSP profiles you should be OK as they have looked at these for interop issues. So UsernameToken, X509 Token, SAML Token, REL Token.

Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
Rimas Rekasius/Chicago/IBM@IBMUS

Rimas Rekasius/Chicago/IBM@IBMUS 05/12/2005 01:41 PM Please respond to basicB2B

To basi...@googlegroups.com cc Subject Constraining the choice of BSP token profile