Enable LDAP for the XMPP 5apps.com vhost #132
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature/123-ejabberd_5apps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
WIP: Enable LDAP on the XMPP 5apps.com vhostto Enable LDAP on the XMPP 5apps.com vhostThis has been executed on andromeda, ready to merge
Enable LDAP on the XMPP 5apps.com vhostto WIP: Enable LDAP on the XMPP 5apps.com vhostDo not merge for now, I found an issue in my VM
Edit: fixed the issue in the last commit
WIP: Enable LDAP on the XMPP 5apps.com vhostto Enable LDAP on the XMPP 5apps.com vhostEnable LDAP on the XMPP 5apps.com vhostto Enable LDAP for the XMPP 5apps.com vhost