[Openid-specs-mobile-profile] MODRNA WG call on March 5th 2018 preliminary minutes

philippe.clement at orange.com philippe.clement at orange.com
Wed Mar 6 09:07:59 UTC 2019

Dear all, please find below the preliminary notes of our call on March 5th 2019. In case of any error or misunderstanding, please let me know.

1.      Roll Call
Bjorn Hjelm (Verizon), John Bradley, Philippe Clement (Orange), Brian, Dave.Tonge (Moneyhub), Geoffrey Graham, Joseph Heenan, Petteri (Ubisecure)
2.      Adoption of the Agenda [Bjorn/John]
3.      External Organizations

  GSMA [Siva]
Not addressed
4.      Working Group Updates

  FAPI WG [Dave]
No update
5.      Spec. Status

  MODRNA CIBA Profile [Dave/Gonzalo/Axel]
No change

  Authentication Profile [Joerg]
No change
6.      Issue Tracker

  MODRNA CIBA Profile<https://bitbucket.org/openid/mobile/issues?status=new&status=open&component=MODRNA%20Profile%20CIBA>  [Dave/Gonzalo/Axel]
  CIBA Core<https://bitbucket.org/openid/mobile/issues?status=new&status=open&component=CIBA> (Post-Implementer's Draft) [Dave/Brian/Gonzalo/Axel]
#85: CIBA: Notifying the Client when a user fails to authenticate<https://bitbucket.org/openid/mobile/issues/85/ciba-notifying-the-client-when-a-user>
Discussions about "access denied" and "failed authentication" error codes.
==>     Joseph to write additional text to the issue, clear the understanding of error messages

#91: CIBA: Authentication request and context parameters<https://bitbucket.org/openid/mobile/issues/91/ciba-authentication-request-and-context>
Ex : geoloc from the smartphone.
Dave mentions 3 options:
     1-We add a section in security considerations
     2-We take the approach that is in the FAPI specs and specify some headers
     3-We specify a different place for implementers to pass context metadata
==>     Consensus of the group on option 1

Petterri: 1 is good. Would we recommend special characteristics for names as parameters ? fully qualified URIs ?
==>     Dave  to put a comment saying that, if standardization is requested, this subject could be revisited.

#150: should auth_req_id have limits on allowable characters?<https://bitbucket.org/openid/mobile/issues/150/should-auth_req_id-have-limits-on>
< . > should be allowed too, consensus on that. Will be added to the spec.

  Authentication Profile<https://bitbucket.org/openid/mobile/issues?status=new&status=open&component=Authentication> [Joerg]
Not addressed
7.      AOB

==>     Bjorn to have a look on all open issues
FAPI working group will be present at EIC-Munich in May. Jointly with MODRNA ?

Next call: to deal with open CIBA issues.

Kind regards,


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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-mobile-profile/attachments/20190306/2a5ab32c/attachment.html>

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