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

philippe.clement at orange.com philippe.clement at orange.com
Fri Apr 24 13:15:20 UTC 2015


Dear all,

Thank you for your remarks, please find below the final notes of our April 22th's call

Participants :
John Bradley
Torsten Lodderstedt
Jorg Connotte
Sebastian Ebling
Bjorn Hjelm

Agenda:
*       Client credential lifecycle mgmt for Native Apps
*       Alignment of GSMA work and authentication draft
*       New working group name
*       AOB

*         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.
client id is obtained at runtime
*         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 the list of acronyms and discussion to continue on mailing list

Postponed:
*       Status of registration spec (esp. software statement contents)
*       Status of discovery design (native vs. web - probably using sequence diagrams)
*       PCR portability across operators


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.

_________________________________________________________________________________________________________________________

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/20150424/1241187e/attachment-0001.html>


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