Add PubSub member affiliation support#3445
Open
romanbsd wants to merge 1 commit into
Open
Conversation
Whitelist access previously treated lingering none affiliations as authorized. Add the standard member affiliation and require an explicit member, publisher, or owner affiliation for whitelist access.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThe pubsub affiliation model now defines member affiliations, exposes a Suggested reviewers: 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
romanbsd
marked this pull request as ready for review
July 21, 2026 10:11
This file contains hidden or 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
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.
Summary
memberaffiliation and support owner affiliation updates to itmember,publisher, orowneraffiliationsnoneaffiliation records from retaining whitelist accessnonerejectionXEP references and rationale
XEP-0060: Publish-Subscribe defines the
memberaffiliation and recommends support for non-required affiliations. Its whitelist access model specifies that an owner should add an entity to the whitelist by assigning thememberaffiliation. It also defines the corresponding service discovery feature ashttp://jabber.org/protocol/pubsub#member-affiliation.XEP-0503: Server-side spaces builds on XEP-0060 and says that a Spaces service SHOULD implement and advertise
member-affiliationfor better usability.Openfire previously had no
memberaffiliation. Its whitelist implementation instead accepted every stored affiliation exceptoutcast. Anoneaffiliation record can remain after membership is removed, which caused that entity to continue being treated as whitelisted. Requiring an explicitmember,publisher, orowneraffiliation aligns whitelist membership with XEP-0060 and makes removal effective.This core support lets consumers such as the Spaces plugin implement and advertise XEP-0503's
member-affiliationrecommendation truthfully.Test plan
./mvnw -pl xmppserver '-P!git-info' -Dtest=WhitelistAccessTest test -nsugit diff --check upstream/main...HEAD