More complete support for custom passwordless connections #2105
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.
Changes
In a previous PR #1981 a new parameter
useCustomPasswordlessConnection
was introduced for the Lock configuration. The reason for that change was that it is possible to create passwordless connections outside of the defaultsms
andemail
. That PR mentions that it can be done via Management API, and it would seem that this includes Terraform (https://github.com/auth0/terraform-provider-auth0) where it seems to be the only way to use passwordless connections.This PR "completes" the above-mentioned PR where the connection parameter in
connection/passwordless/actions.js -> logIn
was still hard-coded to eithersms
oremail
References
Testing
Checklist