<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.idcommons.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=AxelNennker</id>
	<title>IdCommons - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.idcommons.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=AxelNennker"/>
	<link rel="alternate" type="text/html" href="http://wiki.idcommons.com/Special:Contributions/AxelNennker"/>
	<updated>2026-05-28T13:57:32Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.6</generator>
	<entry>
		<id>http://wiki.idcommons.com/index.php?title=Claims_Agent_Teleconference_2011-03-07&amp;diff=4462</id>
		<title>Claims Agent Teleconference 2011-03-07</title>
		<link rel="alternate" type="text/html" href="http://wiki.idcommons.com/index.php?title=Claims_Agent_Teleconference_2011-03-07&amp;diff=4462"/>
		<updated>2011-03-14T08:35:02Z</updated>

		<summary type="html">&lt;p&gt;AxelNennker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A teleconference of the [[Claims Agent Working Group]].&lt;br /&gt;
&lt;br /&gt;
==Logistics==&lt;br /&gt;
* 11AM ET&lt;br /&gt;
&lt;br /&gt;
==Attendees==&lt;br /&gt;
&lt;br /&gt;
# Ariel Gordon&lt;br /&gt;
# Bob Peniero&lt;br /&gt;
# Tom Jones&lt;br /&gt;
# Craig Wittenberg&lt;br /&gt;
# Mary Ruddy&lt;br /&gt;
# Paul Trevithick&lt;br /&gt;
# Peter Watkins&lt;br /&gt;
# Iain Henderson&lt;br /&gt;
# Colin Wallis &lt;br /&gt;
# Susan Morrow&lt;br /&gt;
# John Bradley&lt;br /&gt;
# Patricia Weibe&lt;br /&gt;
# Axel Nennker&lt;br /&gt;
&lt;br /&gt;
==Discussion==&lt;br /&gt;
&lt;br /&gt;
===(1) Overview U-Prove ===&lt;br /&gt;
&lt;br /&gt;
Craig Wittenberg discussed http://microsoft.com/uprove - a summary of the R2 community preview:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;U-Prove agents&amp;quot; are a kind of &amp;quot;claims agent&amp;quot;&lt;br /&gt;
Agents would be run by a variety of providers. We need to work on the governing rules &amp;amp; policies, but we already have a number of parties interested in running agents.&lt;br /&gt;
Each country will probably want to have its own agents running within its borders&lt;br /&gt;
Interoperability across a range of browsers and OSes is very important, so we've tested with about 10 combinations&lt;br /&gt;
We've tested 4-5 browsers on Windows. 3 browsers on OSX. Android, iPhone and Windows Phone 7. &lt;br /&gt;
&lt;br /&gt;
===(2) Demos of U-Prove===&lt;br /&gt;
&lt;br /&gt;
Ariel Gordon shared his screen and did some demos of uProve. These demos are available from http://microsoft.com/uprove. &lt;br /&gt;
&lt;br /&gt;
====Demo #1: Contuso Auctions. Part One: verified car data (from seller)====&lt;br /&gt;
&lt;br /&gt;
Business goal was to improve the UX and decrease the fraud levels on a large scale auction site&lt;br /&gt;
Demo contrasted manually filling in a form vs. retrieving verified car information from the registry of motor vehicles&lt;br /&gt;
U-Prove agent shown was Azure-hosted (cloudapp.net) Silverlight app&lt;br /&gt;
RP: wants Vehicle Year, VIN, Make &amp;amp; Model&lt;br /&gt;
RP trusts several alternative claim providers&lt;br /&gt;
Agent redirects to the user's choice of provider&lt;br /&gt;
User logs in to provider and gets the claims&lt;br /&gt;
The agent displays the values of the claims&lt;br /&gt;
With this (Silverlight) version of the agent you can save the tokens locally on the user's computer&lt;br /&gt;
&lt;br /&gt;
====Demo #2: Contuso Auctions. Part Two: verified bidder====&lt;br /&gt;
&lt;br /&gt;
RP wants these claims: Given name, surnam,e street address, postal code&lt;br /&gt;
Choice of commercial or governmental claims providers&lt;br /&gt;
Bottom line: we are able to leverage real world trust online. We think that this online trust can actually increase real world trust as well&lt;br /&gt;
&lt;br /&gt;
====Demo #3: Unemployment Benefits Agency for the &amp;quot;Yellow&amp;quot; state====&lt;br /&gt;
&lt;br /&gt;
By using verified identity information the state can start putting high value transactions online. &lt;br /&gt;
This is a real scenario that has been discussed with this &amp;quot;yellow&amp;quot; state organization&lt;br /&gt;
Ariel showed the reuse of a previously saved U-Prove token with verified personal information&lt;br /&gt;
&lt;br /&gt;
===Q&amp;amp;A===&lt;br /&gt;
&lt;br /&gt;
* SusanM: What format was the U-Prove token saved? Does it have a specific lifetime?&lt;br /&gt;
* ArielG: In this CTP the information is stored inside of the Silverlight storage area. The format being used is the U-Prove token. As for expiration, the answer is that this is set by the issuer. There are methods to revoke tokens.  &lt;br /&gt;
* ArielG: In the demo any user that has access to my Windows logon has access to my tokens. We can increase the security to binding the tokens to a separate security device. This would also protect against malware that could steal tokens from Silverlight.&lt;br /&gt;
* ArielG did a demo (using the &amp;quot;green&amp;quot; state claim provider) that uses a smartcard as a binding device. For the purposes of the demo we created a smartcard emulator (although at RSA Microsoft did a demo using a real Gemalto smartcard).&lt;br /&gt;
* SusanM: does it work with HTML5 local storage&lt;br /&gt;
* ArielG: We have investigated but didn't use this in the CTP we just released. There were two issues: (i) performance issues with implementing the crypto in JavaScript and (ii) ubiquity of HTML5&lt;br /&gt;
* CraigW: We're not requiring Silverlight. All of these demos work with a plain HTML browser. There are differences of course. With Silverlight the private keys are stored locally only. &lt;br /&gt;
* SandyP: I think there's another Mac/Silverlight bug. &lt;br /&gt;
* ArielG: Please send me the specifics.&lt;br /&gt;
* BobP: What's the different between the U-Prove agent and CardSpace?&lt;br /&gt;
* CraigW: Many of the same themes are there. The core value of user-centric selections, choice, etc. One difference is that CardSpace didn't have U-Prove integrated. Another difference: there is no &amp;quot;introduction mechanism&amp;quot; There are no cards that you have to pre-install. We tried to make it super-easy to NOT require pre-loading of cards. Another difference: there is a cloud-only version (although Avoco and Higgins have done this too). Another difference: broader platform support. &lt;br /&gt;
&lt;br /&gt;
===(3) Microsoft R2 White paper===&lt;br /&gt;
&lt;br /&gt;
* Craig highlighted the white paper available on http://microsoft.com/uprove&lt;br /&gt;
* Starting on page 8 (section 3): we have a simple overview of the architectural elements. &lt;br /&gt;
* Craig showed the level of detail in the white paper especially the swimlanes with and without the Silverlight components&lt;br /&gt;
* Craig highlighted that in the RP security policy there are two completely separate lists: the set of claims vs. the set of trusted claim providers (different/better than CardSpace)&lt;br /&gt;
* Craig walked through many other details &lt;br /&gt;
&lt;br /&gt;
Q&amp;amp;A: &lt;br /&gt;
* Peter: The demos are at the point were the value is obvious. Now we're looking at specific use cases and how the user-centric model is the only way to implement this. But my question is how we could get more collective action on describing and promoting the use cases.  &lt;br /&gt;
* Craig: I agree, but I'm less clear of how to do this.&lt;br /&gt;
* Peter: If you've got some US states behind these demos.&lt;br /&gt;
* Craig: I have been cautious to dive into too much detail. We have had extensive conversations with a number of US states. To your point of use cases, they have very specific use cases they wish to pursue. I have been having these conversations behind the scenes and get the permission of these parties to discuss this. My hope has been to combine the selection of a few use cases and to work on them and make sure that the UX is put into practice, that real users.&lt;/div&gt;</summary>
		<author><name>AxelNennker</name></author>
		
	</entry>
</feed>