I would support 1) clearly defining Implicit as the flow that returns access token from the authorization endpoint ( some people confuses implicit as the flow that returns ID Token in the front channel)
2) Banning the returning of the access token that are not sender constrained from the authorization endpoint Best, Nat Outlook for iOS<https://aka.ms/o0ukef> を入手 ________________________________ 差出人: OAuth <[email protected]> (Dick Hardt <[email protected]> の代理) 送信日時: 水曜日, 11月 28, 2018 8:58 午後 宛先: Hannes Tschofenig Cc: [email protected] 件名: Re: [OAUTH-WG] OAuth Security Topics -- Recommend authorization code instead of implicit +1 While there are various mechanisms to alleviate some of the issues of implicit, I don't think we can recommend specifics, and there may be future ones in the future. I think we all agree that implicit without any mitigation is problematic. How about we recommend against using implicit alone? On Mon, Nov 19, 2018 at 2:34 AM Hannes Tschofenig <[email protected]<mailto:[email protected]>> wrote: Hi all, The authors of the OAuth Security Topics draft came to the conclusion that it is not possible to adequately secure the implicit flow against token injection since potential solutions like token binding or JARM are in an early stage of adoption. For this reason, and since CORS allows browser-based apps to send requests to the token endpoint, Torsten suggested to use the authorization code instead of the implicit grant in call cases in his presentation (see https://datatracker.ietf.org/meeting/103/materials/slides-103-oauth-sessb-draft-ietf-oauth-security-topics-01). A hum in the room at IETF#103 concluded strong support for his recommendations. We would like to confirm the discussion on the list. Please provide a response by December 3rd. Ciao Hannes & Rifaat IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ OAuth mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
