2024-03-13: SP-ICM Minutes
Identity and Consent Management meeting
Attendees (Please add or remove yourself, speakers in bold)
Companies | Attendees |
---|---|
Deutsche Telekom AG | |
Ericsson | |
Gapask | Rajesh Murthy |
KDDI | |
KPN | |
Nokia | |
Orange | |
Simptel | |
Singtel | |
Spry Fox Networks | |
T-Mobile PL | |
T-Mobile US | |
Telefรณnica | Jesรบs Peรฑa Garcรญa-Oliva, Diego Gonzalez Martรญnez, Fabio Garcia, Guido Garcรญa, |
Vodafone | |
ย | Nicholas Venezia |
ย | Kamel Idir |
Camara People @Nick Veneziaย
Agenda
ย
Welcome
Please add or remove yourself from the attendees list
Issues and PRs. Priority discussions (most active issues and/or dependencies for release v0.2):
Profile work https://github.com/camaraproject/IdentityAndConsentManagement/pull/121
New text for offline access / refresh token , now a separate section outside of flows
New text on CIBA optional parameters binding_message, user_code, requested_expiry
New text on id token sub claim
Movedย login_hint format to own section
Broken link in v0.1 of CAMARA-API-access-and-user-consent.md @Herbert Damkerย
Management of opt-out with Implicit consent (legitimate Interest) #138 @Sรฉbastien Dewetย
AoB
Welcome
ย
PR Add missing offline access/refresh token doc from GSMA discussion
It was mentioned during the call whether the information agreed upon and included in the OIDC profile in #121 is sufficient to cover offline access/refresh token usage.
The GSMA documentation could only refer to the CAMARA OIDC profile in the context of the GSMA requirements for Open Gateway off-net scenarios.
It was proposed by @Axel Nennker to close the PR and during the call there were no objections from the call participants to do so (from Telefรณnica/@Jesรบs Peรฑa Garcรญa-Oliva they said they would ok to do so if that is now the WG decision).
The PR was closed during the call itself.
ย
Opt-Outย
We discussed the issue #138 and work continues there.
ย
Purpose
Shilpa is going to create an issue on `purpose`.
Operators are asked whether they have the requirement that multiple purposes in one request are needed.
There are UX issues if the client has to ask for each purpose separately. But still, is this a requirement to ask for multiple purposes?
Axel said that clients should ask for very specific, fine-grained access and not for the mother-of-all-access-tokens and consent for that from the user.
We want to keep the dpv syntax in the profile. Not sure were to put it. Please suggest changes.
ย
Closing Remarks
ย
Axel kindly asked participants to comment on issues and to review PRs and most importantly contribute text changes to PR. WGs thrive only if members become participants. So, again please participate. Please comment and review.
AoB
ย
Next call schedule: March 27, 2024.