Roster Subscription Pre-Approval #4512
Draft
+269
−84
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.
Implementation of RFC 6121 section 3.4: Pre-Approving a Subscription Request https://datatracker.ietf.org/doc/html/rfc6121#section-3.4
To initiate before anything else, a person that wants to smoothly add a new contact for some other person or bot sends
Then proceeds with regular subscription request. If the other entity replies with their own subscription request, our server will then automatically approve it.
Changes in SQL schema
A new column
approvedof type boolean is added torosterusers.