feat(authentication): configurable magicLink dispatch URI, magic token consumption endpoint #722
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 introduces a configurable magic link dispatch URI config option for customizing magic token consumption.
When provided, magic token emails will link to the specified address, instead of the default magic token hook endpoint.
I've also introduced some str nullity check fixes as well as workarounds for trailing slashes.
This PR also modifies internal
redirectUri
behavior.These are no longer appended to the magic link as query params and are retrieved from the token doc instead.
Non-overriden
redirectUri
values are intentionally not stored intoken.data
and coalesced back into latest config values during token retrieval (in hook endpoint).What kind of change does this PR introduce?
Does this PR introduce a breaking change?
The PR fulfills these requirements:
main
branchfix #xxx
, where "xxx" is the issue number)If adding a new feature, the PR's description includes: