feat: add otpiq phone auth provider #1914
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I appreciate the pull request, however we are planning on using auth hooks for these types of integrations. We hope this give users the freedom to choose their provider while lowering the level of commitment required by the auth team. My suggestion would be to take a look at the send SMS hook, if you run into any issues please create an issue: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
Introduce new SMS provider OTPIQ
What is the current behavior?
The available providers are Twilio, MessageBird, Vonage and TextLocal.
Not all of them have WhatsApp and they have regional issue.
What is the new behavior?
Update env variables and the new provider can send sms through Whatsapp and SMS
GOTRUE_SMS_PROVIDER=otpiq
GOTRUE_SMS_OTPIQ_API_KEY=<api_key>
Additional context