<div dir="ltr">"Alice" would be traditional... I have no problem with that if others don't.<div><br></div><div>As for the nature/strength of the digital identity, I think we're going to want to seek some variability in our use cases, most particularly around not assuming "VA" first and foremost, so that we're not too US- or VA-centric. But scenarios in which Alice is strongly authenticated to some standard seem like a reasonable option. And obviously the VA scenario is an important animating one.</div><div><br></div><div>Are there scenarios in which it's useful to enable Alice to be more weakly authenticated on purpose, such as where leveraging existing social logins is a good idea? FWIW, every EHR system I've logged into so far requires passwords alone (with not a lot of evidence of contextual auth that I can see).</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">
<p><b>Eve Maler<br></b>ForgeRock Office of the CTO | VP Innovation & Emerging Technology<br>Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl<br>Join ourĀ <a href="http://forgerock.org/openuma/" target="_blank">ForgeRock.org OpenUMA</a> community!</p></div></div></div></div></div>
<br><div class="gmail_quote">On Mon, Jan 12, 2015 at 2:09 PM, Adrian Gropper <span dir="ltr"><<a href="mailto:agropper@healthurl.com" target="_blank">agropper@healthurl.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Justin,<br><br></div>First and most important: I suggest we call the patient (resource owner) Alice consistently in all use cases.<br><div><br>Then:<br><br>I'm checking on the definition of the patient's digital identity at the VA. Can we agree that the digital identity could be based on federation with an IdP or simply Alice presenting to the VA a secure element manufactured (but not serialized) to an acceptable specification (e.g.: FIDO Alliance U2F). <br><br></div><div>In other words, the basis of a VA-trusted digital identity does not have to be an IdP as long as the technology is sourced from a trusted vendor.<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Adrian<br></div><div><br><br><div><div>-- <br><div><br><div dir="ltr"><br></div></div>
</div></div></div></font></span></div>
<br>_______________________________________________<br>
Openid-specs-heart mailing list<br>
<a href="mailto:Openid-specs-heart@lists.openid.net">Openid-specs-heart@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-heart</a><br>
<br></blockquote></div><br></div>