<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
hey Mike, if true, you are saying the new tabs can 'do everything
the system browser does', so the only difference is UX<br>
<br>
Im not diminishing the importance of the UX , just want to
understand what we gain<br>
<br>
<div class="moz-cite-prefix">On 6/15/15 8:36 AM, Mike Varley wrote:<br>
</div>
<blockquote
cite="mid:BD9B5F5F7BF17E45B0994CB86E1F9BFD8EEED063@DR-EXCH-01.devl.securekey.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
I seem to recall that both iOS and Android will now allow these
embedded web views (i.e., chrome tabs and safari web views) full
access to the user's settings: including cookies, stored
passwords, local storage, (device certificates as John mentioned),
touchID? the works. And there is the improved UI experience as
well, that you pointed out, with "back' buttons that automatically
return the user to the calling App.
<div><br>
</div>
<div>MV<br>
<div><br>
</div>
<div><br>
</div>
<div> <br>
<div>
<div>On Jun 15, 2015, at 8:05 AM, Paul Madsen <<a
moz-do-not-send="true"
href="mailto:paul.madsen@gmail.com">paul.madsen@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div text="#000000" bgcolor="#FFFFFF">John, can you expand
on<br>
<br>
'However it seems like we will be able to do
significantly more with the browser than we had been
thinking.'<br>
<br>
As I see it, the new feature doesn't enable anything
*more* other than a better UX on iOS? True?<br>
<br>
Paul<br>
<br>
<div class="moz-cite-prefix">On 6/12/15 4:38 PM, John
Bradley wrote:<br>
</div>
<blockquote
cite="mid:29050B53-9529-4837-BA79-5F0521879627@ve7jtb.com"
type="cite">
Have a look at 23min into this video from ADC.<br
class="">
<div>
<div class="">
<div class=""><br class="">
</div>
<div class=""><a moz-do-not-send="true"
href="https://developer.apple.com/videos/wwdc/2015/?id=504"
class="" style="font-family: Helvetica;
font-size: 12px; font-style: normal;
font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent:
0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px;">https://developer.apple.com/videos/wwdc/2015/?id=504</a></div>
</div>
</div>
<br class="">
<div class="">This is a significant development.</div>
<div class=""><br class="">
</div>
<div class="">In talking to others from Google
yesterday and today, they have introduced similar
functionality in Android rolling out in
approximately the same timeframe, and backwards
compatible with current versions of Android.</div>
<div class=""><br class="">
</div>
<div class="">Being able to invoke a web tab without
an app flip is a significant change, potentially
making the TA in the browser that we have talked
about the preferred option on iOS.</div>
<div class=""><br class="">
</div>
<div class="">People should look at the ACDC draft <a
moz-do-not-send="true"
href="https://bitbucket.org/openid/napps/wiki/Home"
class="">https://bitbucket.org/openid/napps/wiki/Home</a>.</div>
<div class=""><br class="">
</div>
<div class="">It may be that NAPPS for enterprise is
OAuth using a tab plus PKCE and some additional app
verification logic + fido api in the browser.</div>
<div class="">For SasS we may be able to use OAuth +
ACDC and discovery in a tab.</div>
<div class=""><br class="">
</div>
<div class="">It looks like the tab will have access
to device certificates solving some peoples issues
around that.</div>
<div class=""><br class="">
</div>
<div class="">We should also be able to do <a
moz-do-not-send="true"
href="http://accountchooser.com/" class="">
accountchooser.com</a> in the browser tab to
perform account discovery.</div>
<div class=""><br class="">
</div>
<div class="">Now that the changes have landed on iOS
and Android we should be good to do testing in the
late summer fall.</div>
<div class=""><br class="">
</div>
<div class="">Please start the discussion on the list.</div>
<div class=""><br class="">
</div>
<div class="">I recognize that some people will still
have use cases for native token agents, so I am not
proposing completely eliminating that yet.</div>
<div class=""><br class="">
</div>
<div class="">However it seems like we will be able to
do significantly more with the browser than we had
been thinking.</div>
<div class=""><br class="">
</div>
<div class="">Regards</div>
<div class="">John B.</div>
<div class=""><br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Openid-specs-native-apps mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Openid-specs-native-apps@lists.openid.net">Openid-specs-native-apps@lists.openid.net</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-native-apps">http://lists.openid.net/mailman/listinfo/openid-specs-native-apps</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
Openid-specs-native-apps mailing list<br>
<a moz-do-not-send="true"
href="mailto:Openid-specs-native-apps@lists.openid.net">Openid-specs-native-apps@lists.openid.net</a><br>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-native-apps">http://lists.openid.net/mailman/listinfo/openid-specs-native-apps</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>