2024-05-02: Number verification / SIM Swap / OTP - Meeting Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff:

Community: @Ming Hui Foo @Ludovic Robert @Izahir Clemencia @Axel Nennker @Cormac Hegarty @Huub Appelboom Gregory Liokumovich

Agenda

• Roll Call

• Action Items Review

  • Review of previous meeting minutes

    • If no comment remove DRAFT

• Agenda Bashing

• General Topics

  •  

• Any Other Topics

Minutes

Action Item Review

OTP Validation

ongoing

• Alignement with Mega-Linter done (PR Fixed one-time-password-sms.yaml after megalinter check by bigludo7 · Pull Request #53 · camaraproject/OTPvalidationAPI (github.com) merged)

  • Ask to @Rafal Artych to add MegeLinter check for each PR

• To be done: Shift version from v0.6.0-wip to wip

open point (to be discussed)

• Raised by @Fernando Prado Cabrillo : 

  • Shouldn't we update to "OpenId" as it is normalize across all APIs? the API will still be consumed with a 2-legged token, that is for sure, but I think we should change it and add the Authorization and Authentication section in the API description

SIM Swap

ongoing

• Test case (PR #68 & #70) + issue 63 - Work in progress at CAMARA level to provide Test Definition. Proposal here:  Testing plan for location verification by jlurien · Pull Request #189 · camaraproject/DeviceLocation (github.com) + followed at Commonalities level here: Enhancement of the Testing Guidelines · Issue #158 · camaraproject/Commonalities (github.com) 

• MegaLinter alignement - To be done - Issue #95 - To be checked with @Rafal Artych 

coming

• Alignement of subscription model for Sim-Swap subscription - Work close to be finalized at Commonalities level

Discussion on the version: Probably better to directly target v1.0 with CAMARA meta-release than deliver a v0.5.0

Number Verification

new

• Rename user to subscriber. Triggered here: Rephrase description in yaml · Issue #101 · camaraproject/NumberVerification (github.com)

  •  WIP: clarify description in yaml file by AxelNennker · Pull Request #102 · camaraproject/NumberVerification (github.com)

  • propose test regarding 3-legged-token or replaced by access_token.

    • @Axel Nennker will make a proposal to rephrase (either define 3-legged or other reformulation) and then share this in ICM WG

    • A couple of other APIs use 3-legged word so need ajustement in these as well.

ongoing

• Update Diagram with RFC 9101 to secure the /authorize endpoint

  • Are they still open question preventing to merge Added sequence diagrams with RFC 9101 by mhfoo · Pull Request #94 · camaraproject/NumberVerification (github.com) ?

    • @Ming Hui Foo has answered all questions so far & applied corrections.

    • Team discussion: Wait outcome to the 'purpose' discussion in ICM Purpose Issue to align accordingly the step 7 (using or not rar)

• MegaLinter - Issue #75.

  • PR to fix these here: Fix MegaLinter issues by bigludo7 · Pull Request #103 · camaraproject/NumberVerification (github.com)

• integration to on device application (EAP-AKA) (integration to on device application (EAP-AKA) · Issue #86 · camaraproject/NumberVerification (github.com))

  • Update on GSMA specifications?

    • Timeline has been passed and the document has been approved

    • Document available here: https://www.gsma.com/newsroom/gsma_resources/asac-01-v1-0/ 

  • Issue closed.

Action items