<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Then, my suggestion is to add the
following <br>
<pre style="font-family: 'Courier New', Courier, monospace; font-size: small; text-align: left; padding: 4px; color: rgb(0, 0, 0); background-color: rgb(204, 204, 204); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"> // get_op_browser_state() is an OP defined function
// that returns the browser's login status at the OP.
// How it is done is entirely up to the OP.
</pre>
to the line above <br>
<pre style="font-family: 'Courier New', Courier, monospace; font-size: small; text-align: left; padding: 4px; color: rgb(0, 0, 0); background-color: rgb(204, 204, 204); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"> var opbs = get_op_browser_state();</pre>
Also, add the following <br>
<pre style="font-family: 'Courier New', Courier, monospace; font-size: small; text-align: left; padding: 4px; color: rgb(0, 0, 0); background-color: rgb(204, 204, 204); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"> // Here, the session_state is calculated in this particular way,
// but it is entirely up to the OP how to do it under the
// requirements defined in this specification.
</pre>
to the line above<br>
<pre style="font-family: 'Courier New', Courier, monospace; font-size: small; text-align: left; padding: 4px; color: rgb(0, 0, 0); background-color: rgb(204, 204, 204); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">var ss = CryptoJS.SHA256(client_id + ' ' + e.origin + ' ' +</pre>
Best, <br>
<br>
Nat<br>
<br>
(2013/10/03 14:45), Mike Jones wrote:<br>
</div>
<blockquote
cite="mid:4E1F6AAD24975D4BA5B16804296739437201B56F@TK5EX14MBXC290.redmond.corp.microsoft.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<div class="WordSection1">
<p class="MsoNormal"><span>It’s your points following “Secondly”
that I think we need to capture in the spec and be clear to
developers about – not so much the example itself. If you
can suggest language along that line, that should help
resolve the potential developer confusion that is the real
root of this issue.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>
Thanks,</span></p>
<p class="MsoNormal"><span>
-- Mike</span></p>
<p class="MsoNormal"><span> </span></p>
<div>
<div>
<p class="MsoNormal"><b><span>From:</span></b><span>
n-sakimura [<a class="moz-txt-link-freetext" href="mailto:n-sakimura@nri.co.jp">mailto:n-sakimura@nri.co.jp</a>]
<br>
<b>Sent:</b> Wednesday, October 02, 2013 10:34 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><br>
<b>Subject:</b> Re: [Openid-specs-ab] [Bitbucket] Issue
#872: session 4.1. Opbs is unclear and conflict with
"session management memo" on wiki (openid/connect)</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">First of all, opbs is just a parameter
name that I happened to have used in the example. It could
have been anything.
<br>
<br>
Sencondly, what is being stored in the OP Browser State
completely depends on each OP. It may just be a random
variable that the OP relates the server side state and the
browser. Alternatively, it may be storing bunch of state
related variables which is then signed or encrypted for the
server to be less stateful. <br>
<br>
I do not want to give false impression to the developpers
that there is one single way of doing it. The maximum I am
willing to do is to add some comments to the example.
<br>
<br>
Nat<br>
<br>
(2013/10/03 9:50), Mike Jones wrote:</p>
</div>
<blockquote>
<div>
<p class="MsoNormal">P.S. Nat, if you could provide
proposed text giving a few examples of what Opbs might
contain and (if we’re not already saying this) what
properties this state needs to have, that would be really
useful in helping to close this issue.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">
Thanks,</p>
<p class="MsoNormal">
-- Mike</p>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal"><b>From:</b>
<a moz-do-not-send="true"
href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a>
[<a moz-do-not-send="true"
href="mailto:openid-specs-ab-bounces@lists.openid.net">mailto:openid-specs-ab-bounces@lists.openid.net</a>]
<b>On Behalf Of </b>Mike Jones<br>
<b>Sent:</b> Wednesday, October 02, 2013 5:47 PM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><br>
<b>Subject:</b> Re: [Openid-specs-ab] [Bitbucket]
Issue #872: session 4.1. Opbs is unclear and conflict
with "session management memo" on wiki
(openid/connect)</p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I strongly disagree with removing the
example. I believe it’s the only thing giving
implementers a sense of what they need to do to fulfill
the requirements.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">We should do what it takes to clarify
the example, if needed – not remove it.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">
-- Mike</p>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal"><b>From:</b> Nat Sakimura [<a
moz-do-not-send="true"
href="mailto:issues-reply@bitbucket.org">mailto:issues-reply@bitbucket.org</a>]
<br>
<b>Sent:</b> Wednesday, October 02, 2013 5:26 PM<br>
<b>To:</b> Mike Jones<br>
<b>Subject:</b> Re: [Bitbucket] Issue #872: session
4.1. Opbs is unclear and conflict with "session
management memo" on wiki (openid/connect)</p>
</div>
</div>
<p class="MsoNormal"> </p>
<table class="MsoNormalTable" width="100%">
<tbody>
<tr>
<td>
<table class="MsoNormalTable" width="100%">
<tbody>
<tr>
<td>
<div>
<table class="MsoNormalTable" width="100%">
<tbody>
<tr>
<td>
<table class="MsoNormalTable"
width="100%">
<tbody>
<tr>
<td width="32">
<br>
</td>
<td id="content">
<table
class="MsoNormalTable"
width="100%">
<tbody>
<tr>
<td colspan="2">
<p
class="MsoNormal"><strong>Nat
Sakimura</strong>
commented on
issue #872:
</p>
</td>
</tr>
<tr>
<td colspan="2">
<p
class="MsoNormal"><b><a
moz-do-not-send="true"
href="https://bitbucket.org/openid/connect/issue/872/session-41-opbs-is-unclear-and-conflict">session
4.1. Opbs is
unclear and
conflict with
"session
management
memo" on wiki</a>
</b></p>
</td>
</tr>
<tr>
<td colspan="2">
<p>Did not even
needed to follow
up with Breno.
My intention
here is clear.
The example is
non-normative
and is just
illustrating
what an OP might
do to fulfill
what the spec.
normatively
requires. If it
is causing more
confusion than
explaining it,
we may want to
drop the example
and just go with
the normative
text.</p>
</td>
</tr>
<tr>
<td nowrap="nowrap">
<p
class="MsoNormal">Status:</p>
</td>
<td width="100%">
<p
class="MsoNormal"><span
class="old"><s>new</s></span>
<span
class="new">open</span>
</p>
</td>
</tr>
<tr>
<td><br>
</td>
<td><br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td>
<p class="MsoNormal"><a
moz-do-not-send="true"
href="https://bitbucket.org/openid/connect/issue/872/session-41-opbs-is-unclear-and-conflict">View
this issue</a> or add a
comment by replying to this
email.
</p>
</td>
</tr>
</tbody>
</table>
</div>
</td>
</tr>
<tr>
<td>
<table class="MsoNormalTable" width="100%">
<tbody>
<tr>
<td>
<p class="MsoNormal"><a
moz-do-not-send="true"
href="https://bitbucket.org/openid/connect/issue/872/unwatch/mbj/6ee343dc8521bd44c690cfa4ae5fe8299cabd061/">Unwatch
this issue</a> to stop receiving
email updates.
</p>
</td>
<td><br>
</td>
<td width="100">
<p class="MsoNormal"><a
moz-do-not-send="true"
href="https://bitbucket.org"><span></span></a></p>
<br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><a moz-do-not-send="true"
href="https://bitbucket.org"><span> </span></a></p>
</div>
<p class="MsoNormal"><a moz-do-not-send="true"
href="https://bitbucket.org"><span><br>
<br>
<br>
</span></a></p>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span>_______________________________________________</span></a></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span>Openid-specs-ab mailing list</span></a></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span><u><span>Openid-specs-ab@lists.openid.net</span></u></span></a></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span><u><span>http://lists.openid.net/mailman/listinfo/openid-specs-ab</span></u></span></a></pre>
</blockquote>
<p class="MsoNormal"><a moz-do-not-send="true"
href="https://bitbucket.org"><span><br>
<br>
<br>
</span></a></p>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span>-- </span></a></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span>Nat Sakimura (<u><span>n-sakimura@nri.co.jp</span></u>)</span></a></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span>Nomura Research Institute, Ltd. </span></a></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span><u><span>Tel:+81-3-6274-1412</span></u> Fax:+81-3-6274-1547</span></a></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span> </span></a></pre>
<pre><span><a moz-do-not-send="true" href="https://bitbucket.org"><span>本メールに含まれる情報は機密情報であり、宛先に記載されている方のみに送信することを意図しております。意図された受取人以外の方によるこれらの情報の開示、複製、再配布や転送など一切の利用が禁止されています。誤って本メールを受信された場合は、申し訳ござ</span><span>ӓ</span></a></span></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span> 6;|</span></a></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span>14;</span><span>せんが、送信者までお知らせいただき、受信されたメールを削除していただきますようお願い致します。</span><span></span></a></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span>PLEASE READ:</span></a></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span>The information contained in this e-mail is confidential and intended for the named recipient(s) only.</span></a></pre>
<pre><a moz-do-not-send="true" href="https://bitbucket.org"><span>If you are not an intended recipient of this e-mail, you are hereby notified that any review, dissemination, distribution or duplication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete your copy from your system.</span></a></pre>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Nat Sakimura (<a class="moz-txt-link-abbreviated" href="mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>)
Nomura Research Institute, Ltd.
Tel:+81-3-6274-1412 Fax:+81-3-6274-1547
本メールに含まれる情報は機密情報であり、宛先に記載されている方のみに送信することを意図しております。意図された受取人以外の方によるこれらの情報の開示、複製、再配布や転送など一切の利用が禁止されています。誤って本メールを受信された場合は、申し訳ございませんが、送信者までお知らせいただき、受信されたメールを削除していただきますようお願い致します。
PLEASE READ:
The information contained in this e-mail is confidential and intended for the named recipient(s) only.
If you are not an intended recipient of this e-mail, you are hereby notified that any review, dissemination, distribution or duplication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete your copy from your system.
</pre>
</body>
</html>