Enable LDAP for the XMPP 5apps.com vhost #132
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
lightning
Lightning address, lndhub, etc.
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#132
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.
Refs #123
@@ -81,0 +125,4 @@admin_users = ["greg@5apps.com","sebastian@5apps.com","garret@5apps.com",I don't think any other pro customer would have their users get global admin accounts for the entire Kosmos XMPP server.
I also think that these should come from an encrypted data bag, because I don't see any benefits to publishing admin account data, but only drawbacks.
Good point, I have moved the admin users to an encrypted data bag
@@ -26,0 +28,4 @@ldap_base: "ou=<%= host[:name] %>,<%= @ldap_base %>"ldap_filter: "(nsRole=cn=xmpp_role,ou=<%= host[:name] %>,<%= @ldap_base %>)"<% end -%><% end -%>Why should we add content to the main config file instead of adding separate files for every vhost?
I was considering using different files for the vhosts, but then I could not find a way to define the hosts all at once (https://docs.ejabberd.im/admin/configuration/#host-names), so it didn't seem to make much sense to split the config. I'm going to look into what's possible
So just because of a single additional line per host it doesn't make sense to split out all the rest?
I don't quite follow to be honest.
I have moved each vhost's config to its own file
This has been executed on andromeda, ready to merge
Do not merge for now, I found an issue in my VM
Edit: fixed the issue in the last commit
Enable LDAP on the XMPP 5apps.com vhostto Enable LDAP for the XMPP 5apps.com vhost