Hi Paul,

Sorry for not so active to updating this document.
I have heard that InCommon or Internet2 is experimenting SAML/OpenID interop similar to what this document covers.
They might focus more on authentication assertions not authentication policies. Do you know about the experiment?

I have found some typo in the document:

1. preferred_authn_policies -> preferred_auth_policies
2. In composing a SAML AuthnRequest message to the chosen IdP, the OP should take the PAPE policy URI from the OpenID request and map into an appropriate SAML <RequestedAuthnContext><AuthnContextClassRef> value.

-> "the OP SHOULD take"

I am joining the government PoC project now and proposing to use this document
as guideline to implement a SAML/OpenID proxy. We are organizing a forum
to discuss this. The members includes major mobile carriers and integrators.
I am trying to gather their opinions about this document. I need a few more
weeks to do that.

If Concordia DG is not in harry to finish up this document, I'd like to have more time to do that job and proposing some inputs based on players
in Japan.

Thank you.
Tatsuki
Tatsuki Sakushima
NRI Pacific - Nomura Research Institute America, Inc.

(2/3/10 12:51 AM), Paul Madsen wrote:

Hi, I've had an AI for a while to rev the deployment guideline to reflect the SAML LOA profile and the ICAM OpenID profile.

New version at

http://kantarainitiative.org/confluence/display/concordia/Deployment+Guide+for+Proxying+Assurance+between+OpenID+and+SAML

When the SAML LOA profile becomes available for public review, I'd hope Concordia can vote this doc out for the same

Thanks

Paul
_______________________________________________
DG-Concordia mailing list
DG-Concordia@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/dg-concordia

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.733 / Virus Database: 271.1.1/2668 - Release Date: 02/04/10 14:35:00