2024-07-25: Number Verification/ SIM Swap / OTP- Meeting Minutes
Community Attendees:
@Ludovic Robert @Gregory Lindner @Jorge Garcia Hospital @Izahir Clemencia @Axel Nennker @Huub Appelboom
LF Staff:
Agenda
Antitrust Policy
Action Items Review
Review of previous meeting minutes (July 11th)
If no comment remove Draft - No comment
Open item will be review below for each API
Other topics
Minutes
OTP Validation
New
Rename repository from OTPvalidationAPI to OTPValidation (#75)
Ongoing
Preparation of the Meta Release
Ready for Release Candidate 1 (PR74)
Readiness checklist
yaml (version v1rc1)
CHANGELOG.md
README.MD
Done
added user story
added test definition
Action for the meta release
See above
SIM Swap
New
Adding User Story (PR125) - 2 stories - In progress btw Gregory & Jorge.
Add Readiness checklist (same PR)
Finalize Test definitions (PR70)
@Fernando Prado Cabrillo covered @Toyeeb Rehman and @Gregory Lindner suggestions → pending review
Send a 451 instead of 200 API code - When the SIM Swap date is greater than the max historic days that the Telco allows, for privacy reasons (Issue124)
Should not be 200
451 should be discussed in Commonalities
reintroducing monitoredPeriod could be discussed moving forward - We will not introduce this for the Meta Release 1.
PR for the Release of v1.0.0-rc (Release of API version 1.0.0-rc.1
We need to manage the fact that simswap-subscription will not be part of the MR
Let use the 'cheaper' way to do it by crafting a branch without the YAML
@Ludovic Robert & @Jorge Garcia Hospital has to inform @Fernando Prado Cabrillo
Ongoing
Request body is required but all properties are optional
Still open in commonalities
for meta release we leave request body as required and force the client to send an empty body -> {}
Extracting phoneNumber from the 3-legg access token (issue117)
see proposal in the issue.
Discussion about introducing this for the meta-relase
To be consistent with KYC-Match: Error responses alignment with Commonalities by rartych · Pull Request #115 · camaraproject/KnowYourCustomer (github.com) we probably have to do it for the second meta-release.
@Huub Appelboom raised a good point about potential use of SIM swap to perform a numberVerification
Need to be discussed in Commonalities because must be enforced for all our APIs.
Make sense to be shared also with the OpenGateway Product
@Axel Nennker would trigger the issue to Commonalities
Done
Remove unused errors & aligned with commonalities error
Updated sim-swap-subscriptions
Action for the meta release
Number Verification
New
Ongoing
Add user story (PR118)
Waiting from @Axel Nennker or @Fernando Prado Cabrillo approval
Release preparation (PR121)
Readiness checklist
yaml (version v1rc1)
CHANGELOG.md
README.MD
Test Definition - Progress from@Axel Nennker --> PR soon.
Done
Action for the meta release