Save email verification token to person's pod #5
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.
To do this, person has to prepare their pod by creating a settings file that notification service identity has write or append access to. The service also needs read access to every file that participates in the discovery, in particular personal hospex profile.
The settings are discovered as follows:
<webId> space:preferencesFile <settings> .
<webId> <https://example.com/emailVerificationToken> "token" .
the predicate for token discovery is editable in config, but should be kept consistent