Agenda

Antitrust Policy

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

• Action Items Review

  • Review of previous meeting minutes (May 16th)

    • If no comment remove Draft

  • Open item will be review below for each API

Minutes

OTP Validation

New

• Git Hub MegaLinter workflow integrated.

• Align securitySchemes and Auth description with commonalities and ICM #56

  • Current discussion in ICM to slightly change the 'statement' (info description)

    • Proposal from ICM should come before end of next week

• Provide test definition artefacts #57

  • Assigne: @Ludovic Robert 

    • ping @Izahir Clemencia 

  • PR59 open to create TD folder

• Prepare API for CAMARA meta release 1 #58

  • Placeholder issue to prepare the release

  • see Meta-release Fall24
    Milestones M3 & M4 in particular

Ongoing

Backlog

SIMSwap

New

• Align sim-swap notification subscription Yaml with new subscription model #108

  • Subscription model validated.

• Prepare API for CAMARA meta release 1 #109

  • Placeholder issue to prepare the release

  • see Meta-release Fall24
    Milestones M3 & M4 in particular

Ongoing

• Add API-Name aka wild-card scope #103

  • To be discussed

    • Need update on the yaml as my understanding is that "There will be no "API level" scope unless explicitly defined in the API Spec YAML file".

      • Ref: (1) Scope at "API level" feedback from country market implementation · Issue #95 · camaraproject/IdentityAndConsentManagement (github.com)

      • "a scope would only provide access to all endpoints and resources of an API if it is explicitly defined in the API Spec YAML file and agreed in the corresponding API subproject if it makes sense."

      • PR to be checked and merged

• Submission of Test Case #68 #70

  • Assignee: @Fernando Prado Cabrillo 

• Git Hub MegaLinter workflow integration

  • PR110 to be approved (@Fernando Prado Cabrillo )

Backlog

Number Verification

New

• Submission of Test Case #104

  • PR for folder creation to be merged (#105)

  • Assignee: @Axel Nennker 

• OAuth2 Authorization Code vs OIDC Authorization Code (#106)

  • Alignement with ICM ruling → OAuth2 Authorization Code vs OIDC Authorization Code · Issue #163 · camaraproject/IdentityAndConsentManagement (github.com)

  • @Axel Nennker will create a PR to fix this one. Done.

• Prepare API for CAMARA meta release 1 #107

  • Placeholder issue to prepare the release

  • see Meta-release Fall24
    Milestones M3 & M4 in particular

• Git Hub MegaLinter workflow integration

  • PR108 to be approved (@Fernando Prado Cabrillo )

Ongoing

• Added sequence diagrams with RFC 9101 (issue #93 & PR94)

  • @Cormac Hegarty update ?

    • OK from Cormac

    • PR to be merged

• Clarification on the yaml file for user & subscriber (issue #101 & PR102)

  • @Axel Nennker update?

    • Approved & merged.

Backlog

•  integration to on device application (EAP-AKA) (#86)

  • no update

Action items