<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Helvetica, Arial, sans-serif">However, if the user is
using iCloud keychain, then their credentials should be filled in
for the user so not too bad. The issue, is that if account is
using 2FA the user will have to do the 2FA dance for every app.
That could be a pain.<br>
<br>
Thanks,<br>
George<br>
</font><br>
<div class="moz-cite-prefix">On 6/13/17 5:57 PM, Justin Richer via
Openid-specs-ab wrote:<br>
</div>
<blockquote cite="mid:DCFCE203-D3C8-479F-A935-43F8C351DC2E@mit.edu"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
This has nothing to do with OIDC’s session management, but rather
sessions in the browser itself. From what I understand, the
per-app silos would prevent the OP from knowing it’s the same user
coming in from different apps, since they wouldn’t have access to
the session and cookie jar. So the UX degrades rather poorly as
the user is prompted to log in separately to their identity
provider (with primary credentials) from every single app.
<div class=""><br class="">
</div>
<div class=""> — Justin</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jun 13, 2017, at 5:40 PM, rich levinson via
Openid-specs-ab <<a moz-do-not-send="true"
href="mailto:openid-specs-ab@lists.openid.net" class="">openid-specs-ab@lists.openid.net</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""> Hi Nat, et
al,<br class="">
<br class="">
I am not sure I understand why this situation should
cause anything to "break".<br class="">
<br class="">
Let me explain my view of this situation, in the context
of general session mgmt,<br class="">
which is the following:<br class="">
<br class="">
In the "OpenID Connect Session Management 1.0" spec:<br
class="">
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://openid.net/specs/openid-connect-session-1_0.html">http://openid.net/specs/openid-connect-session-1_0.html</a><br
class="">
it says:<br class="">
<blockquote class="">
<pre class="">"In OpenID Connect, the session at the RP typically starts
when the RP validates the End-User's ID Token.
...
When the OP supports session management, it MUST also return the Session State
as an additional session_state parameter in the Authentication Response.
...
This parameter is:
session_state
Session State.
JSON [RFC7159] string that represents the End-User's login state at the OP.
It MUST NOT contain the space (" ") character.
This value is opaque to the RP.
This is REQUIRED if session management is supported.
The Session State value is initially calculated on the server."
</pre>
</blockquote>
This indicates that the OP has knowledge of the
End-User's login state at the OP.<br class="">
However, this login state is independent of the "session
at the RP", which is<br class="">
created when the client app (RP) rcv's the identity
token which, in the protocol,<br class="">
is well after the End-User logged in at the OP.<br
class="">
<br class="">
Later in the spec, section 5, it is also stated that:<br
class="">
<blockquote class="">
<pre class="">"5. RP-Initiated Logout
An RP can notify the OP that the End-User has logged out of the site and
might want to log out of the OP as well.
In this case, the RP, after having logged the End-User out of the RP,
redirects the End-User's User Agent to the OP's logout endpoint URL.
This URL is normally obtained via the end_session_endpoint element
of the OP's Discovery response or may be learned via other mechanisms."
</pre>
</blockquote>
This basically confirms the supposition above that the
OP login and the RP session are<br class="">
effectively independent entities.<br class="">
<br class="">
Now, let's consider the case where a 2nd RP decides to
start a session w the same End-User,<br class="">
presumably, a 2nd RP on the same device where the 1st RP
established a session.<br class="">
<br class="">
When the 2nd RP sends the Authentication Request to the
OP's /authorize endpoint,<br class="">
it seems obvious to me that the OP knows the End-User is
logged in and would have<br class="">
no problem issuing a 2nd id-token to the 2nd RP, w/o
re-logging in the End-User.<br class="">
<br class="">
Assuming this is the case, then I do not understand why
ios-11, by "siloing" the apps<br class="">
prevents the OP from issuing new id-tokens to each app,
all under the original<br class="">
OP-login by the End-User.<br class="">
<br class="">
Am I missing something?<br class="">
<br class="">
Thanks,<br class="">
Rich<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">On 6/12/2017 8:04 PM, Nat
Sakimura via Openid-specs-ab wrote:<br class="">
</div>
<blockquote type="cite"
cite="mid:CABzCy2CFKAjmkNOszaPJ991DnsQ9JBiCuVd8HHBfLveknA7wRA@mail.gmail.com"
class="">
<div dir="ltr" class="">Maybe we can call upon the
privacy community as well raising the voice that
this is very bad for privacy.
<div class="">I wonder what is the privacy
enhancement they have in mind. </div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="">On Fri, Jun 9, 2017 at 2:34
AM 'Iain McGinniss' via OIDF Account Chooser list
<<a
href="mailto:oidf-account-chooser-list@googlegroups.com"
moz-do-not-send="true" class="">oidf-account-chooser-list@googlegroups.com</a>>
wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr" class="">Hello all,
<div class=""><br class="">
</div>
<div class="">Just to bring this to your
attention: Apple has essentially killed single
sign-on for native apps in iOS 11. Changes
made to SFSafariViewController (used by
AppAuth, and the recommended mechanism for
federated login by Apple) now mean that
browser state is partitioned per app, so there
is no way for an existing authentication in
the browser to be reused by an app.</div>
<div class=""><br class="">
</div>
<div class="">This fundamentally breaks an
important part of OpenID Connect - users will
now need to re-authenticate with their IDP in
every app that they use. There is still time
to provide feedback to Apple on this change,
though they have been discussing this change
in terms of "enhancing privacy" and I'd be
very surprised if they change tack now.</div>
<div class=""><br class="">
</div>
<div class="">Iain</div>
</div>
-- <br class="">
<br class="">
--- <br class="">
You received this message because you are
subscribed to the Google Groups "OIDF Account
Chooser list" group.<br class="">
To unsubscribe from this group and stop receiving
emails from it, send an email to <a
href="mailto:oidf-account-chooser-list+unsubscribe@googlegroups.com"
target="_blank" moz-do-not-send="true" class="">oidf-account-chooser-list+unsubscribe@googlegroups.com</a>.<br
class="">
For more options, visit <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=nNxUKneeZofWTyt9qclOUTeEg29NkEkknFyDupoNiiA&m=z6H6MqLIToKnju5TQdKnYOa6pGD9lyMxhwLO-mdMgac&s=XtvXRyjw8QvajPlQD8M0d6xQJnp_3jK9zv_hDOXEOXY&e="
target="_blank" moz-do-not-send="true" class="">https://groups.google.com/d/optout</a>.<br
class="">
</blockquote>
</div>
<div dir="ltr" class="">-- <br class="">
</div>
<div data-smartmail="gmail_signature" class="">
<p dir="ltr" class="">Nat Sakimura</p>
<p dir="ltr" class="">Chairman of the Board, OpenID
Foundation</p>
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre class="" wrap="">_______________________________________________
Openid-specs-ab mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openid.net_mailman_listinfo_openid-2Dspecs-2Dab&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=nNxUKneeZofWTyt9qclOUTeEg29NkEkknFyDupoNiiA&m=z6H6MqLIToKnju5TQdKnYOa6pGD9lyMxhwLO-mdMgac&s=tYftjD7QNKeiH9oZIyspoUu_QX44iHnFoAzyiuQapmg&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openid.net_mailman_listinfo_openid-2Dspecs-2Dab&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=nNxUKneeZofWTyt9qclOUTeEg29NkEkknFyDupoNiiA&m=z6H6MqLIToKnju5TQdKnYOa6pGD9lyMxhwLO-mdMgac&s=tYftjD7QNKeiH9oZIyspoUu_QX44iHnFoAzyiuQapmg&e=</a>
</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br
class="">
Openid-specs-ab mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Openid-specs-ab@lists.openid.net" class="">Openid-specs-ab@lists.openid.net</a><br
class="">
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Openid-specs-ab mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
</pre>
</blockquote>
<br>
</body>
</html>