Every LDAP account should have access to XMPP #140
Closed
opened 2020-02-20 16:17:58 +00:00 by greg
·
4 comments
No Branch/Tag Specified
Labels
Clear labels
monitoring
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
service
discourse
Kosmos Community Forums
Infrastructure metrics, alerts, notifications, etc.
service
accounts
Kosmos Accounts
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
mastodon
kosmos.social
service
nostr
Relays, Blossom server, etc.
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
release
major
release
minor
release
patch
All your base are belong to us
User interface, process design, etc.
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#140
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Remove the filtered role from the ejabberd config
Follow-up to #123
This has revealed a flaw in the new directory structure. If we remove the filtering altogether, LDAP read-only accounts for the wiki and xmpp become valid XMPP accounts.
Right now my solution is to turn these accounts from a
personto aorganizationalPerson. Then the filter would look like this (aperson, but not anorganizationalPerson). In LDAP anorganizationalPersonis also apersonsince it's "subclassing" it.The ACIs will also need to be updated to add the
objectClassattribute to the list of allowed attributes for the read-only account, because they are not part of the list for nowSo why are they a "Person" in the first place? They're not people (also not "organizational people"), so shouldn't they be something else?
I found a good solution. LDAP accounts used to filter users will be moved be under
cn=applications,dc=kosmos,dc=org, for example theuid=xmpp,ou=kosmos.org,cn=applications,dc=kosmos,dc=orgaccount. Then everything undercn=users,dc=kosmos,dc=orgare actual users/peopleACIs need to be set on the Organizational Units to allow the applications accounts to perform the searches
Closing this one now that ejabberd has been upgraded and restarted yesterday. The config change in #141 had not been applied, this has been fixed in #142