Many thanks Conor
Yes, of course, I should have remembered that…doh!
So I best go ask the folks with implementations inspired by ID-WSF
such as…… Lasso? .. TAS3? ..(actually even some of our own dev work
in NZ from days gone by and resurrected recently so we are kind of completing the
circle..).
Good pointer Conor.
Cheers
Colin
From: Cahill, Conor P [mailto:]
Sent: Friday, 14 January 2011 11:11 a.m.
To: Colin Wallis; ''
Subject: RE: wss-SAMLTokenProfile-v1.1
Colin,
This is the specification incorporated by Liberty in their web
services framework. So any Liberty framework would be following this
profile.
It is referenced in the ID-WSF
2.0 SecMech SAML Profile specification.
Conor
From: Colin Wallis [mailto:]
Sent: Thursday, January 13, 2011 4:33 PM
To: ''
Subject: [saml-dev] FW: wss-SAMLTokenProfile-v1.1
Hi all
I didn't get a response over at WS-SX-Dev….. wondering
if anyone here has a view on this…
Cheers
Colin
From: Colin Wallis
Sent: Thursday, 13 January 2011 4:20 p.m.
To: ''
Subject: wss-SAMLTokenProfile-v1.1
Greetings and a Happy New year everyone
I probably don't have the most appropriate list for this
query but hoping someone can help.
How does the rest of world see this profile? Has anybody
implemented this standard? What is its level of adoption?
It appears, that in some architectural review done here in
the NZ Gov, it's been unearthed that we hand coded something akin to this
profile, and we now have a chance to make amends and use the actual profile..
Question is, is there sufficient adoption of it to make the
investment in resources to make the switch worthwhile?
Any thoughts folks?
Cheers
Colin
Colin Wallis
Authentication Standards Manager,
Government Technology Services
Department of Internal Affairs
New Zealand Government
PO Box 10-526, Wellington 6143
New Zealand
t: +64 4 463 1337
m: +64 27 244 7135
Alternative email:
====
CAUTION: This email message and any attachments contain information that
may be confidential and may be LEGALLY PRIVILEGED. If you are not the intended
recipient, any use, disclosure or copying of this message or attachments is
strictly prohibited. If you have received this email message in error please
notify us immediately and erase all copies of the message and attachments.
Thank you.
====
====
CAUTION: This email message and any attachments contain
information that may be confidential and may be LEGALLY PRIVILEGED. If you are
not the intended recipient, any use, disclosure or copying of this message or
attachments is strictly prohibited. If you have received this email message in
error please notify us immediately and erase all copies of the message and
attachments. Thank you.
====
