[Openid-specs-mobile-profile] Typos in OpenID Connect MODRNA Client initiated Backchannel Authentication Flow

Brian Campbell bcampbell at pingidentity.com
Fri Oct 19 16:17:52 UTC 2018


Issue raised https://bitbucket.org/openid/mobile/issues/99/typos-in-ciba

On Fri, Oct 19, 2018 at 9:09 AM Dave Tonge <dave.tonge at momentumft.co.uk>
wrote:

> Thanks Takahiko!
> I'll raise an issue and we'll get these fixed shortly.
>
> Dave
>
> On Wed, 17 Oct 2018 at 21:22, Takahiko Kawasaki <taka at authlete.com> wrote:
>
>> Hello,
>>
>> I found some typos in "OpenID Connect MODRNA Client initiated Backchannel
>> Authentication Flow"
>> (draft-mobile-client-initiated-backchannel-authentication).
>>
>>
>> p.3, Consumption Device
>>
>> (e.g. at a Bank teller) ->
>> (e.g. at a bank teller)
>>
>>
>> p.5, the last paragraph
>>
>> whenever the OpenID Provider receive an dynamic registration request ->
>> whenever the OpenID Provider receives a dynamic registration request
>>
>>
>> p.6, the second paragraph
>>
>> to demonstrate that such "jws_uri" ->
>> to demonstrate that such "jwks_uri"
>>
>>
>> p.7, the first paragraph
>>
>> from an dynamic registration ->
>> from a dynamic registration
>>
>>
>> p.7, the second last paragraph
>>
>> unqiue identifier ->
>> unique identifier
>>
>>
>> p.8, CIBA Ping Mode diagram
>>
>> The "OP" block is broken on the line "(3) CIBA Ping Callback".
>>
>>
>> p.9, CIBA Push Mode diagram
>>
>> The "OP" block is broken on the line "(3) CIBA Push Callback".
>>
>>
>> p.11, the third line of the entity body of the example
>>
>> acr_values=mod-mf&x ->
>> ac_values=mod-mf&
>>
>>
>> p.11, 7.1.1., the first paragraph
>>
>> request JWT is passes as an ->
>> request JWT is passed as an
>>
>>
>> p.15, 8., The first paragraph
>>
>> After ... and the OP identifies ... ->
>> After ..., the OP identifies ...
>>
>>
>> p.16, 10.
>>
>> (Poll Ping or Push) ->
>> (Poll, Ping or Push)
>>
>>
>> p.18., 10.1.1., the first paragraph
>>
>> an ID Token, Access Token ->
>> an ID Token, an Access Token
>>
>>
>> p.18, 10.2., the first paragraph
>>
>> send a "POST HTTP Request" ->
>> send an "HTTP POST Request"
>>
>>
>> p.19, the second paragraph
>>
>> sent as a HTTP POST ->
>> sent as an HTTP POST
>>
>>
>> p.19, the third paragraph (after the example)
>>
>> return a HTTP 401 ->
>> return an HTTP 401
>>
>>
>> p.19, the fourth paragraph
>>
>> with a HTTP 204 ->
>> with an HTTP 204
>>
>>
>> p.20, the last paragraph, the first line
>>
>> bind the ID Token, Access Token and the auth_req_id ->
>> bind the ID Token, the Access Token and the auth_req_id
>>
>>
>> p.20, the last paragraph, the fourth line,
>>
>> the ID too ->
>> the ID Token, too
>>
>>
>> p.21, the first paragraph
>>
>> sent as a HTTP POST ->
>> sent as an HTTP POST
>>
>>
>> p.21, the second paragraph (after the example)
>>
>> SHOULD return a HTTP 401 ->
>> SHOULD return an HTTP 401
>>
>>
>> p.21, the fourth paragraph
>>
>> The Client MUST ensure that that the auth_req_id ->
>> The Client MUST ensure that the auth_req_id
>>
>>
>> p.21, the fifth paragraph
>>
>> validate the access token received in request using ->
>> validate the access token in the response using
>>
>>
>> If a refresh token is present in the request ->
>> If a refresh token is present in the response
>>
>>
>> p.22, the first paragraph
>>
>> For valid requests, he Client ->
>> For valid requests, the Client
>>
>>
>> with a HTTP 204 ->
>> with an HTTP 204
>>
>>
>> p.23, 12., the second paragraph
>>
>> Agent through which send the error to the Client ->
>> Agent through which the error is sent to the Client
>>
>>
>> p.23, 12., the third paragraph
>>
>> to the client ->
>> to the Client
>>
>>
>> Add a period at the end of the sentence.
>>
>>
>> p.24, 13., the third paragraph
>>
>> I How Sector Identifier Validation is done ->
>> How Sector Identifier Validation is done
>>
>>
>> In OpenId Dynamic ->
>> In OpenID Dynamic
>>
>>
>> p.25, 14., the third paragraph
>>
>> How this check in done is outside the scope ->
>> How this check is done is outside the scope
>>
>>
>> p.25, 15., the first paragraph
>>
>> theirs number being leaked ->
>> their numbers being leaked
>>
>> p.29, the first paragraph
>>
>> it is decrypted by the CardManger ->
>> it is decrypted by the CardManager ->
>>
>>
>> if everything is ok ->
>> If everything is ok
>>
>>
>>
>>
>> Best Regards,
>> Takahiko Kawasaki
>> Authlete, Inc.
>>
>> _______________________________________________
>> Openid-specs-mobile-profile mailing list
>> Openid-specs-mobile-profile at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile
>>
>
>
> --
> Dave Tonge
> CTO
> [image: Moneyhub Enterprise]
> <http://www.google.com/url?q=http%3A%2F%2Fmoneyhubenterprise.com%2F&sa=D&sntz=1&usg=AFQjCNGUnR5opJv5S1uZOVg8aISwPKAv3A>
> Moneyhub Financial Technology, 5th Floor, 10 Temple Back, Bristol, BS1 6FL
> t: +44 (0)117 280 5120
>
> Moneyhub Enterprise is a trading style of Moneyhub Financial Technology
> Limited which is authorised and regulated by the Financial Conduct
> Authority ("FCA"). Moneyhub Financial Technology is entered on the
> Financial Services Register (FRN 809360) at fca.org.uk/register. Moneyhub Financial
> Technology is registered in England & Wales, company registration number
> 06909772 .
> Moneyhub Financial Technology Limited 2018 ©
>
> DISCLAIMER: This email (including any attachments) is subject to
> copyright, and the information in it is confidential. Use of this email or
> of any information in it other than by the addressee is unauthorised and
> unlawful. Whilst reasonable efforts are made to ensure that any attachments
> are virus-free, it is the recipient's sole responsibility to scan all
> attachments for viruses. All calls and emails to and from this company may
> be monitored and recorded for legitimate purposes relating to this
> company's business. Any opinions expressed in this email (or in any
> attachments) are those of the author and do not necessarily represent the
> opinions of Moneyhub Financial Technology Limited or of any other group
> company.
> _______________________________________________
> Openid-specs-mobile-profile mailing list
> Openid-specs-mobile-profile at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile
>

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-mobile-profile/attachments/20181019/ff4020ba/attachment-0001.html>


More information about the Openid-specs-mobile-profile mailing list