[Openid-specs-ab] Issue #883: Order of the description about iframe (openid/connect)

Ryo Ito ritou.06 at gmail.com
Wed Oct 16 02:22:25 UTC 2013

Hi Mike,

I modified your Word file and attached it.
My suggestion is simply, each contents of 4.1 and 4.2 are not changed, and
RP iframe is explained earlier.

- The RP developer will understand a request and the response of
postMessage necessary for implementation in section 4.1.
- And the OP developer will understand the method of its verification


2013/10/16 Mike Jones <Michael.Jones at microsoft.com>

> Hi Ryo,
> I tried to figure out exactly what you wanted last night while preparing
> the release candidates, and realized that I wasn't sure.  It would be good
> to get this updated by the time we publish final specifications for Core,
> etc.
> Could you do me a favor?  I've attached a Word version of the current
> Session spec with tracked changes turned on.  Could you edit it into the
> form that you'd like it to be and send it back to me?
> Don't worry about grammar or section numbers.  I realize that English
> grammar is difficult, what with the plurals and articles not present in
> Japanese.  I'll sort that out.  Beyond reordering the sections, which I
> understand, I'd like to know what kind of text changes you had in mind to
> connect the sections together and make the description easier to understand
> and flow better.
>                                 Thanks,
>                                 -- Mike
> -----Original Message-----
> From: openid-specs-ab-bounces at lists.openid.net [mailto:
> openid-specs-ab-bounces at lists.openid.net] On Behalf Of Ryo Ito
> Sent: Monday, October 07, 2013 1:38 AM
> To: openid-specs-ab at lists.openid.net
> Subject: [Openid-specs-ab] Issue #883: Order of the description about
> iframe (openid/connect)
> New issue 883: Order of the description about iframe
> https://bitbucket.org/openid/connect/issue/883/order-of-the-description-about-iframe
> Ryo Ito:
> I think that the order of the description about iframe should reverse.
> The implementer may be easy to understand a description along the real
> data flow (OP -> RP -> RP iframe -> OP iframe -> RP iframe...)
> ===
> 4. Session Status Change Notification
> - Two iframe is necessary for this implementation
> - RP iframe knows id of OP iframe
> - Polling by repeating postMessage
> 4.1 RP iframe
> - This iframe MUST know the ID of the OP iframe so that it can postMessage
> to the OP iframe.
> - The postMessage includes client_id and session_state
> - The received data would either be changed or unchanged.
> 4.2 OP iframe
> - The OP iframe has access to Browser state at the OP...
> - The OP iframe MUST recalculate it from the previously obtained Client
> ID, the source origin URL (from the postMessage), and the current OP
> Browser state.
> - The response is ...
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab

Ryo Ito
Email : ritou.06 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20131016/a807d265/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openid-connect-session-1_0-16_ryo.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 50607 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20131016/a807d265/attachment-0001.docx>

More information about the Openid-specs-ab mailing list