<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Nat, et al,<br>
<br>
I am not sure I understand why this situation should cause anything
to "break".<br>
<br>
Let me explain my view of this situation, in the context of general
session mgmt,<br>
which is the following:<br>
<br>
In the "OpenID Connect Session Management 1.0" spec:<br>
<a 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>
it says:<br>
<blockquote>
<pre>"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>
However, this login state is independent of the "session at the RP",
which is<br>
created when the client app (RP) rcv's the identity token which, in
the protocol,<br>
is well after the End-User logged in at the OP.<br>
<br>
Later in the spec, section 5, it is also stated that:<br>
<blockquote>
<pre>"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>
effectively independent entities.<br>
<br>
Now, let's consider the case where a 2nd RP decides to start a
session w the same End-User,<br>
presumably, a 2nd RP on the same device where the 1st RP established
a session.<br>
<br>
When the 2nd RP sends the Authentication Request to the OP's
/authorize endpoint,<br>
it seems obvious to me that the OP knows the End-User is logged in
and would have<br>
no problem issuing a 2nd id-token to the 2nd RP, w/o re-logging in
the End-User.<br>
<br>
Assuming this is the case, then I do not understand why ios-11, by
"siloing" the apps<br>
prevents the OP from issuing new id-tokens to each app, all under
the original<br>
OP-login by the End-User.<br>
<br>
Am I missing something?<br>
<br>
Thanks,<br>
Rich<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 6/12/2017 8:04 PM, Nat Sakimura via
Openid-specs-ab wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABzCy2CFKAjmkNOszaPJ991DnsQ9JBiCuVd8HHBfLveknA7wRA@mail.gmail.com">
<div dir="ltr">Maybe we can call upon the privacy community as
well raising the voice that this is very bad for privacy.
<div>I wonder what is the privacy enhancement they have in
mind. </div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">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">oidf-account-chooser-list@googlegroups.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hello all,
<div><br>
</div>
<div>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><br>
</div>
<div>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><br>
</div>
<div>Iain</div>
</div>
-- <br>
<br>
--- <br>
You received this message because you are subscribed to the
Google Groups "OIDF Account Chooser list" group.<br>
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">oidf-account-chooser-list+unsubscribe@googlegroups.com</a>.<br>
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">https://groups.google.com/d/optout</a>.<br>
</blockquote>
</div>
<div dir="ltr">-- <br>
</div>
<div data-smartmail="gmail_signature">
<p dir="ltr">Nat Sakimura</p>
<p dir="ltr">Chairman of the Board, OpenID Foundation</p>
</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="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>
</body>
</html>