W3C home > Mailing lists > Public > public-xg-webid@w3.org > December 2011

RE: xmas present for w3c

From: Peter Williams <home_pw@msn.com>
Date: Sun, 25 Dec 2011 22:49:12 -0800
Message-ID: <SNT143-W56B530FE02ACD92915EAB992AE0@phx.gbl>
To: "public-xg-webid@w3.org" <public-xg-webid@w3.org>

For a bit more fun, ran a best practice WIF application in the Azure Simulator, having received an assertion from the bridge network (webid to openid to ws-fedp to local API)... ultimately sourced to ODS, a webid and an act of https client authn. Obviously, its just a matter or publishing the code to the real azure cloud for anyone to try it out. Someone wants a zip file, to replicated the project, let me know. http://tinyurl.com/7zgwjyb There is obviously NOTHING semantic web aware about this application. its just USING the webid infrastructure as authentication mechanism. Hopefully, this kind of thing would helps drive lots of adoption (since there can be now as many adoptees and drivers of webid adoption as their of folks building WIF applications on the micosoft platform). to talk to the webid world all folks have to do is run a wizard that talks to the Azure bridge, and set up the Azure bridge to bridge to the like of ODS - who proxy openid to webid validation agents. To: public-xg-webid@w3.org
Date: Sun, 25 Dec 2011 19:43:01 -0800
Subject: xmas present for w3c

I was very wary about having anything to do with W3C, given its reputation for endless argument. But, its hard to deny facts. In my post http://yorkporc.wordpress.com/2011/12/25/ods-to-sourceforce-azure-pingfederate-wif-and-shib/ I documented getting from ODS with webid to sourceforce, Azure, realty, and then to Shib. unlike my previous trials, I simply used only ODS software (using an opera browser), using nothing from windows.
When I look at the potential now for client certs, I see a rosy future. Its not just a smardcard proxy now. The cert in a client authn role is now a full featured member of the (modern) claims world.
Received on Monday, 26 December 2011 06:49:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:39:50 UTC