[Openid-specs-mobile-profile] MODRNA WG call on Oct 9th 2018 preliminary minutes
bcampbell at pingidentity.com
Tue Oct 9 18:51:43 UTC 2018
I apologize for not being fully attentive on the call. I had to meet with a
contractor during the same time period and was trying to multitask and do
both. But didn't do either very well.
So just one comment/clarification with respect to "Brian mentions possible
confusions of langage in open id connect core himself to look at." - I'd
only wanted to say that there had been a couple issues related to
id_token_hint raised recently in Connect Core (linked below) but that I
didn't think they had any bearing on the CIBA hints. That may not have
actually been relevant to the conversation at that point but that was my
On Tue, Oct 9, 2018 at 9:27 AM <philippe.clement at orange.com> wrote:
> Please find below the preliminary notes of our call on Oct 9th 2018.
> In any case of error or misunderstanding, please let me know.
> *Roll Call* (extract from GotoMeeting)
> Bjorn Hjelm
> Dave.Tonge (Moneyhub)
> Philippe Clement (Orange)
> Bjorn Hjelm (Verizon)
> Brian Campbell (Ping)
> Geoff Graham
> Petteri (Ubisecure)
> Michael Engan
> Charles Marais (Orange)
> *Adoption of the Agenda [Bjorn/John]*
> *Issue Tracker*
> *CIBA [Dave/Brian/Gonzalo/Axel]*
> *#86: CIBA needs IANA Considerations*
> Pull request 24 and 25 address metadata and parameters and solve some
> error codes with invalid_grant (from OAuth2). To double check.
> *#91: CIBA: Authentication request and context parameters*
> open by Petteri following last call, not resolved yet.
> *#92: update/fix ID Token examples in CIBA Authentication Results*
> Pull request done, a review is wishable.
> *#93: use Public Claim Names for CIBA JWT claims*
> Pull request done.
> *Globally, *edition of pull requests need to be achieved to solve issues
> #94, #95, #81, #62, #71, #85
> The question to split the drafts hopefully for the next call is asked.
> - Dave and Brian to work on.
> Brian mentions possible confusions of langage in open id connect core
> himself to look at.
> Best 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.
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged
material for the sole use of the intended recipient(s). Any review, use,
distribution or disclosure by others is strictly prohibited. If you have
received this communication in error, please notify the sender immediately
by e-mail and delete the message and any file attachments from your
computer. Thank you._
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openid-specs-mobile-profile