[Openid-specs-mobile-profile] OpenID Connect Mobile Profile WG Call April 22

Lodderstedt, Torsten t.lodderstedt at telekom.de
Wed Apr 22 15:57:56 UTC 2015


Hi Philippe,

please find my comments inline (Prefix TLT: ).

Best regards,
Torsten.

Von: philippe.clement at orange.com [mailto:philippe.clement at orange.com]
Gesendet: Mittwoch, 22. April 2015 17:21
An: Lodderstedt, Torsten; openid-specs-mobile-profile at lists.openid.net
Betreff: OpenID Connect Mobile Profile WG Call April 22

Dear all,

Please find below the preliminary notes of our today's call
The hearing was not good for some participants, so please apologies if some things are missing. In this case, please update.

Participants (to check):
John Bradley
TLT: Gonzalo Fernandéz
Torsten Lodderstedt
Jorg Connotte
TLT: Sebastian Ebling
Bjorn Helm

·         Client credential lifecycle mgmt for Native Apps
Option 1: One client_id static for all instances of the app
Option 2: one different client_id per app instance

Alternate option: optimization of version 1 and 2: the RP sends a SS (Software Statement) to retrieve a client_ID
Up to the MNO to issue different or same client_ID on different instances of the same app. From client side, no difference.

John discussed on the OAuth list: way for the RP of passing the SS by reference.
RP could send a URI to the relevant MNO
Discussions about revocation

Software Statement should be issued at development time, provided from MNO dev portal to RP.

 TLT: client id is obtained at runtime (see my posting)
·         Status of registration spec (esp. software statement contents)
Not addressed
·         Status of discovery design (native vs. web - probably using sequence diagrams)
Not addressed
·         Alignment of GSMA work and authentication draft
GSMA: questions going on the "how to implement"
Meeting  tomorrow with Gautam
A common member of OIF and GSMA can post issues to our WG mailing list

·         New working group name
Remove « attributes »
Torsten to distribute final list of acronyms

Best regards,
Philippe


_________________________________________________________________________________________________________________________



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/20150422/d01275ca/attachment.html>


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