Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GSMA OGW Product WS - Subscription/notification mechanism for SIM SWAP formal request #47

Closed
jgarciahospital opened this issue Jul 19, 2023 · 1 comment · Fixed by #60
Labels
enhancement New feature or request

Comments

@jgarciahospital
Copy link
Collaborator

Problem description
Formal inclusion of the GSMA OGW Product WS request to include Subscription/notification mechanism as part of OGW services.

camaraproject/Commonalities#8 (comment)

Possible evolution
SIM SWAP API, as many other current APIs, may be enhanced by a subscription mechanism that will enable different use cases, e.g.:

  • Antifraud mechanism may require being notified by the operator when a SIM is affected by a swap procedure, implementing different mechanisms to avoid fraud (e.g., warm or confirm with the user).

The proposal includes examples or proposal for input-outputs of such mechanism, to be discussed and aligned with the current service API.

Alternative solution
N/A

Additional context
More details included in the formal request file, attached
Camara Submission - Subscription_Notifications v2.docx

@jgarciahospital jgarciahospital added the enhancement New feature or request label Jul 19, 2023
@bigludo7
Copy link
Collaborator

bigludo7 commented Sep 7, 2023

As discussed in team meeting Sept 7th

  • We agreed that this feature must be added.
  • This feature will be managed in the SimSwap API Family.
  • We have to decide if we want to have the SimSwap Notification Subscription is the same yaml than current one (checkSimSwap.camara.swagger.yaml) or have a separate yaml.

@DT-DawidWroblewski @gregory1g and @bigludo7 already provided their preference for a distinct yaml as we perceive this as a distinct product.

Looking for team feedback as it would be great to have decision on this topic for next meeting (Sept 21th)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants