<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div><font color="#1F497D">Dear all,</font></div>
<div><font color="#1F497D"> </font></div>
<div><font color="#1F497D">In addition to the meeting today, the meeting notes from the FAPI WG meeting in London can be found at <a href="https://bitbucket.org/openid/fapi/wiki/FAPI_Meeting_Notes_2017-11-06"><font color="blue"><u>https://bitbucket.org/openid/fapi/wiki/FAPI_Meeting_Notes_2017-11-06</u></font></a></font></div>
<div> </div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">Best regards,</span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">Philippe</span></font></div>
<div><font face="Tahoma" size="2"><span style="font-size:10pt;">_____________________________________________<br>
<b>De :</b> CLEMENT Philippe IMT TECHNO <br>
<b>Envoyé :</b> mardi 28 novembre 2017 17:26<br>
<b>À :</b> Hjelm, Bjorn; openid-specs-mobile-profile@lists.openid.net<br>
<b>Objet :</b> MODRNA WG Call on nov 28th 2017 preliminary minutes</span></font></div>
<div> </div>
<div> </div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">Dear all,</span></font></div>
<div> </div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">Please find below the preliminary minutes of our call. In case of any error or misunderstanding, please let me know.</span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;"> </span></font></div>
<div> </div>
<div><font face="Arial" size="2"><span style="font-size:10pt;"><u>Participants</u> : John, Petteri, Siva, Bjorn, Alex Chong, Dave Tonge, Gonzalo,</span></font></div>
<div> </div>
<ol style="margin:0;">
<font face="Arial" size="2"><span style="font-size:10pt;">
<li style="margin-top:5pt;margin-bottom:5pt;"><u>Roll Call</u></li><li style="margin-top:5pt;margin-bottom:5pt;"><u>Adoption of the Agenda</u> </li></span></font>
</ol>
<ol start="3" style="margin:0;">
<font face="Arial" size="2"><span style="font-size:10pt;">
<li><font face="Wingdings">à</font> adopted. </li></span></font>
</ol>
<div> </div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">One item added: update from IETF meeting 2 weeks ago: Security doc adopted, concerns token binding for ID token and Access token.</span></font></div>
<ol start="4" style="margin:0;">
<font face="Arial" size="2"><span style="font-size:10pt;">
<li style="margin-top:5pt;margin-bottom:5pt;"><u>Liaisons Updates</u></li></span></font>
</ol>
<ul style="margin:0;">
<font face="Arial" size="2"><span style="font-size:10pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">GSMA [Siva]</li><li style="margin-top:5pt;margin-bottom:5pt;"> </li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Wingdings">à</font> CPAS call: One query regarding login_hint_token expiry time. CPAS proposes to include it into the LHT. Will be discussed in next CPAS call. We have to look also at error messages
in this case. Do we have to create an error if the LHT is valid ? the objective would be to control how long the client can cache the LHT. (For information, the client credentials management process is supposed to evolve in MC). Error should be more specific
than “invalid request”. Or a sub type could be added to explain the real error case.</li></span></font>
</ul>
<ul style="margin:0;padding-left:72pt;">
<font face="Arial" size="2"><span style="font-size:10pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">questions about hashing claims with SHA256 for attribute services, to protect data. Probably outside the OIDC protocol. Discussion to continue on CPAS side. Use cases to mention to FAPI group.</li></span></font>
</ul>
<ul style="margin:0;">
<font face="Arial" size="2"><span style="font-size:10pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Back channel and front channel are concerned. UK Open Banking flows use mostly front channel redirect. FAPI looks for CIBA in cases where redirects through front channel are not operating. </li></span></font>
</ul>
<ol start="4" style="margin:0;">
<li style="margin-top:5pt;margin-bottom:5pt;"> </li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2"><span style="font-size:10pt;"><u>Working Group Updates</u></span></font></li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2"><span style="font-size:10pt;">Feedback from FAPI meeting in London (Dave & John)</span></font></li></ol>
<ul style="margin:0;padding-left:72pt;">
<font face="Arial" size="2"><span style="font-size:10pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Looking a way to add additional claims to ID token. Dave to post a proposal to the list.</li></span></font>
</ul>
<div style="margin-top:5pt;margin-bottom:5pt;"> </div>
<ol start="7" style="margin:0;">
<font face="Arial" size="2"><span style="font-size:10pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Issue Tracker [All]</li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Wingdings">à</font> not addressed</li></span></font>
</ol>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2"><span style="font-size:10pt;">Best regards,</span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2"><span style="font-size:10pt;">Philippe</span></font></div>
<div><font color="#365F91"> </font></div>
<div> </div>
</span></font>
<PRE>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>