Finished GNP Auth and SimSwap MVP implementation #475
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a number of features which have been led by the addition of the first Ericsson Global Network Platform API from Vonage - SimSwap.
Description
In order to use SimSwap, a new handler for credentials has been introduced - GnpHandler and a new credentials type, Gnp. These credentials hold the registered subscriber number and extend off the Keypair object.
GNP requires an OAuth flow, which has been implemented within the GnpHandler object. Please note that a lot of this behaviour is for internals only, and should never need to be modified by the end developer.
You can find more information on what the Handler is doing here:
https://developer.vonage.com/en/api/camara/auth
Motivation and Context
Evolution of Vonage SDKs and APIs
How Has This Been Tested?
New test suite added for both GNP handlers and SimSwap
Example Output or Screenshots (if appropriate):
Types of changes
Checklist: