- Service APIs for “IdentityAndConsentManagement” (see APIBacklog.md)
- Telco operator exposure platforms implementing CAMARA APIs should be built with a privacy-by-default approach to fully comply with data protection regulations, such as the GDPR regulation in Europe, which emphasises on user privacy. These regulations note that some CAMARA APIs may require user consent to be accessed. This forces the operators to provide means and appropriate solutions to capture, store and manage this consent through its lifecycle. Otherwise, the scoped CAMARA APIs cannot be rolled out in production networks. Building such a solution also means bringing in scope the identity of the end user and/or the subscriber (as both could be different) and making sure that end user experience of using the API is not compromised while doing so.
- Describe, develop, document and test the APIs (with 1-2 Telcos)
- Started: March 2023
- Location: virtually
Identity and Consent Management
Scope
Meetings
- Meetings are held virtually
- Schedule: bi-weekly, Wednesday, 4 PM CET/CEST (15:00 UTC, 14:00 UTC during European DST). For next call, see minutes of previous meetings
- Meeting link: Microsoft Teams Meeting
Results
- Current Version: v0.1.0 WIP
- API definition
- API documentation
- For changes see CHANGELOG.md
Contributorship and mailing list
- To subscribe / unsubscribe to the mailing list of this Sub Project and thus be / resign as Contributor please visit https://lists.camaraproject.org/g/sp-icm.
- A message to all Contributors of this Sub Project can be sent using sp-icm@lists.camaraproject.org.
GitHub repository
- To view the GitHub repository for this Sub Project, please visit https://github.com/camaraproject/IdentityAndConsentManagement.