Commit 7849b53f authored by Noe Nieto's avatar Noe Nieto 💬

Merge branch 'master' of source.puri.sm:liberty/ldh_developer

parents ffbf577a 972dc3e6
......@@ -44,3 +44,8 @@
ldh_nginx_ssl_key_src_path: "cert_keys/{{ ansible_fqdn }}.key.plain"
ldh_nginx_ssl_key_path: "/etc/ssl/private/{{ ansible_fqdn }}.key.plain"
ldh_nginx_log_error: true
# Location of Debian file used to install Keel/LDH. Uncomment next
# line and update the absolute path where you stored your .deb
# file.
# ldh_deb_file: /tmp/ldh-middleware_latest.deb
......@@ -153,6 +153,11 @@ Role Variables
used to create the SSL certificate. Default value:
`/etc/ssl/private/example.com.key.plain`
* `ldh_deb_file`
Absolute path of .deb file that Ansible will use to install
Keel/LDH. Default value: `/tmp/ldh-middleware_latest.deb`
Dependencies
------------
......
......@@ -43,3 +43,5 @@ ldh_nginx_ssl_cert_path: "/etc/ssl/certs/example.com.crt"
ldh_nginx_ssl_key_src_path: "cert_keys/example.com.key.plain"
ldh_nginx_ssl_key_path: "/etc/ssl/private/example.com.key.plain"
ldh_nginx_https_redirect: "https://example.com"
ldh_deb_file: /tmp/ldh-middleware_latest.deb
......@@ -8,7 +8,7 @@
- name: Install ldh_middleware from .deb
apt:
deb: /tmp/ldh-middleware_0.0.2_amd64.deb
deb: "{{ ldh_deb_file }}"
- name: Copy sample link_profile to config location
copy:
......@@ -64,18 +64,21 @@
template:
src: templates/nginx/purist_middleware.j2
dest: /etc/nginx/sites-available/purist_middleware
notify: "restart nginx"
- name: Copy SSL cert for nginx
copy:
src: "{{ ldh_nginx_ssl_cert_src_path }}"
dest: "{{ ldh_nginx_ssl_cert_path }}"
when: ldh_nginx_use_https
notify: "restart nginx"
- name: Copy SSL key for nginx
copy:
src: "{{ ldh_nginx_ssl_key_src_path }}"
dest: "{{ ldh_nginx_ssl_key_path }}"
when: ldh_nginx_use_https
notify: "restart nginx"
- name: enable ldh_middleware web for nginx
file:
......
---
- name: Simple Prosody role for Keel/LDH
hosts: all
become: yes
roles:
- role: ldh_prosody
vars:
ldh_prosody_ldap_uri: "ldap://ldap.freedom.test/"
ldh_prosody_ldap_base: "ou=people,dc=freedom,dc=test"
ldh_prosody_domain: "freedom.test"
Keel/LDH Prosody
================
This role installs and configures an instance of
[Prosody](https://prosody.im/) with basic funcitonality:
* Uses self signed certificates created at the time of the
installation.
* Does not allow registration.
* Authenticates users against Keel/LDH LDAP instance via Cyrus SASL.
* Connections to LDAP instance are not encrypted.
Requirements
------------
This role has only been tested with Ansible 2.7.1.
Role Variables
--------------
* `ldh_prosody_ldap_uri`
URI used by Prosody to connect to the LDAP server. Default value:
`ldap://ldap.example.com/`.
* `ldh_prosody_ldap_base`
Search starting point used by Prosody when querying the
LDAP. Default value: `ou=people,dc=example,dc=com`.
* `ldh_prosody_domain`
Name of the domain Prosody will serve. Default value:
`example.com`
Dependencies
------------
This role does not depend on other roles.
License
-------
AGPL-3.0-or-later
Author Information
------------------
Purism SPC <liberty@puri.sm>
Homepage: https://source.puri.sm/liberty/ldh_developer
---
# defaults file for ldh_prosody
ldh_prosody_required_pkgs:
- prosody
- sasl2-bin
- lua-cyrussasl
- libsasl2-modules-ldap
ldh_prosody_ldap_uri: "ldap://ldap.example.com/"
ldh_prosody_ldap_base: "ou=people,dc=example,dc=com"
ldh_prosody_domain: "example.com"
#
# Settings for saslauthd daemon
# Please read /usr/share/doc/sasl2-bin/README.Debian for details.
#
# Should saslauthd run automatically on startup? (default: no)
START=yes
# Description of this saslauthd instance. Recommended.
# (suggestion: SASL Authentication Daemon)
DESC="SASL Authentication Daemon"
# Short name of this saslauthd instance. Strongly recommended.
# (suggestion: saslauthd)
NAME="saslauthd"
# Which authentication mechanisms should saslauthd use? (default: pam)
#
# Available options in this Debian package:
# getpwent -- use the getpwent() library function
# kerberos5 -- use Kerberos 5
# pam -- use PAM
# rimap -- use a remote IMAP server
# shadow -- use the local shadow password file
# sasldb -- use the local sasldb database file
# ldap -- use LDAP (configuration is in /etc/saslauthd.conf)
#
# Only one option may be used at a time. See the saslauthd man page
# for more information.
#
# Example: MECHANISMS="pam"
MECHANISMS="ldap"
# Additional options for this mechanism. (default: none)
# See the saslauthd man page for information about mech-specific options.
MECH_OPTIONS="/etc/saslauthd.conf"
# How many saslauthd processes should we run? (default: 5)
# A value of 0 will fork a new process for each connection.
THREADS=5
# Other options (default: -c -m /var/run/saslauthd)
# Note: You MUST specify the -m option or saslauthd won't run!
#
# WARNING: DO NOT SPECIFY THE -d OPTION.
# The -d option will cause saslauthd to run in the foreground instead of as
# a daemon. This will PREVENT YOUR SYSTEM FROM BOOTING PROPERLY. If you wish
# to run saslauthd in debug mode, please run it by hand to be safe.
#
# See /usr/share/doc/sasl2-bin/README.Debian for Debian-specific information.
# See the saslauthd man page and the output of 'saslauthd -h' for general
# information about these options.
#
# Example for chroot Postfix users: "-c -m /var/spool/postfix/var/run/saslauthd"
# Example for non-chroot Postfix users: "-c -m /var/run/saslauthd"
#
# To know if your Postfix is running chroot, check /etc/postfix/master.cf.
# If it has the line "smtp inet n - y - - smtpd" or "smtp inet n - - - - smtpd"
# then your Postfix is running in a chroot.
# If it has the line "smtp inet n - n - - smtpd" then your Postfix is NOT
# running in a chroot.
OPTIONS="-c -m /var/run/saslauthd"
pwcheck_method: saslauthd
mech_list: PLAIN
\ No newline at end of file
---
# handlers file for ldh_prosody
- name: restart prosody
service:
name: prosody
state: restarted
- name: restart saslauthd
service:
name: saslauthd
state: restarted
galaxy_info:
author: Purism SPC
description: Basic Prosody role for LDH development.
company: Purism SPC
license: AGPL-3.0-or-later
min_ansible_version: 2.7.1
galaxy_tags:
- prosody
- xmpp
dependencies: []
# List your role dependencies here, one per line. Be sure to remove the '[]' above,
# if you add dependencies to this list.
---
# tasks file for ldh_prosody
- name: Install required Prosody packages
apt:
name: "{{ ldh_prosody_required_pkgs }}"
update_cache: yes
cache_valid_time: 600
state: present
- name: Add prosody user to sasl group
user:
name: prosody
groups: sasl
append: yes
- name: Copy and configure prosody.cfg.lua
template:
src: etc/prosody/prosody.cfg.lua.j2
dest: /etc/prosody/prosody.cfg.lua
notify: "restart prosody"
- name: Copy and configure /etc/saslauthd.conf
template:
src: etc/saslauthd.conf.j2
dest: /etc/saslauthd.conf
notify: "restart saslauthd"
- name: Copy config file /etc/default/saslauthd
copy:
src: etc/default/saslauthd
dest: /etc/default/saslauthd
notify: "restart saslauthd"
- name: Create /etc/sasl2 directory
file:
path: /etc/sasl2
state: directory
mode: 0755
- name: Copy config file /etc/sasl2/xmpp.conf
copy:
src: etc/sasl2/xmpp.conf
dest: /etc/sasl2/xmpp.conf
notify: "restart saslauthd"
-- Prosody Example Configuration File
--
-- Information on configuring Prosody can be found on our
-- website at http://prosody.im/doc/configure
--
-- Tip: You can check that the syntax of this file is correct
-- when you have finished by running: luac -p prosody.cfg.lua
-- If there are any errors, it will let you know what and where
-- they are, otherwise it will keep quiet.
--
-- The only thing left to do is rename this file to remove the .dist ending, and fill in the
-- blanks. Good luck, and happy Jabbering!
---------- Server-wide settings ----------
-- Settings in this section apply to the whole server and are the default settings
-- for any virtual hosts
-- This is a (by default, empty) list of accounts that are admins
-- for the server. Note that you must create the accounts separately
-- (see http://prosody.im/doc/creating_accounts for info)
-- Example: admins = { "user1@example.com", "user2@example.net" }
admins = { }
-- Enable use of libevent for better performance under high load
-- For more information see: http://prosody.im/doc/libevent
--use_libevent = true;
-- This is the list of modules Prosody will load on startup.
-- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
-- Documentation on modules can be found at: http://prosody.im/doc/modules
modules_enabled = {
-- Generally required
"roster"; -- Allow users to have a roster. Recommended ;)
"saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.
"tls"; -- Add support for secure TLS on c2s/s2s connections
"dialback"; -- s2s dialback support
"disco"; -- Service discovery
-- Not essential, but recommended
"private"; -- Private XML storage (for room bookmarks, etc.)
"vcard"; -- Allow users to set vCards
-- These are commented by default as they have a performance impact
--"privacy"; -- Support privacy lists
--"compression"; -- Stream compression (Debian: requires lua-zlib module to work)
-- Nice to have
"version"; -- Replies to server version requests
"uptime"; -- Report how long server has been running
"time"; -- Let others know the time here on this server
"ping"; -- Replies to XMPP pings with pongs
"pep"; -- Enables users to publish their mood, activity, playing music and more
"register"; -- Allow users to register on this server using a client and change passwords
-- Admin interfaces
"admin_adhoc"; -- Allows administration via an XMPP client that supports ad-hoc commands
--"admin_telnet"; -- Opens telnet console interface on localhost port 5582
-- HTTP modules
--"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
--"http_files"; -- Serve static files from a directory over HTTP
-- Other specific functionality
"posix"; -- POSIX functionality, sends server to background, enables syslog, etc.
--"groups"; -- Shared roster support
--"announce"; -- Send announcement to all online users
--"welcome"; -- Welcome users who register accounts
--"watchregistrations"; -- Alert admins of registrations
--"motd"; -- Send a message to users when they log in
--"legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
};
-- These modules are auto-loaded, but should you want
-- to disable them then uncomment them here:
modules_disabled = {
-- "offline"; -- Store offline messages
-- "c2s"; -- Handle client connections
-- "s2s"; -- Handle server-to-server connections
};
-- Disable account creation by default, for security
-- For more information see http://prosody.im/doc/creating_accounts
allow_registration = false;
-- Debian:
-- send the server to background.
--
daemonize = true;
-- Debian:
-- Please, don't change this option since /var/run/prosody/
-- is one of the few directories Prosody is allowed to write to
--
pidfile = "/var/run/prosody/prosody.pid";
-- These are the SSL/TLS-related settings. If you don't want
-- to use SSL/TLS, you may comment or remove this
ssl = {
key = "/etc/prosody/certs/localhost.key";
certificate = "/etc/prosody/certs/localhost.crt";
}
-- Force clients to use encrypted connections? This option will
-- prevent clients from authenticating unless they are using encryption.
c2s_require_encryption = false
-- Force certificate authentication for server-to-server connections?
-- This provides ideal security, but requires servers you communicate
-- with to support encryption AND present valid, trusted certificates.
-- NOTE: Your version of LuaSec must support certificate verification!
-- For more information see http://prosody.im/doc/s2s#security
s2s_secure_auth = false
-- Many servers don't support encryption or have invalid or self-signed
-- certificates. You can list domains here that will not be required to
-- authenticate using certificates. They will be authenticated using DNS.
--s2s_insecure_domains = { "gmail.com" }
-- Even if you leave s2s_secure_auth disabled, you can still require valid
-- certificates for some domains by specifying a list here.
--s2s_secure_domains = { "jabber.org" }
-- Select the authentication backend to use. The 'internal' providers
-- use Prosody's configured data storage to store the authentication data.
-- To allow Prosody to offer secure authentication mechanisms to clients, the
-- default provider stores passwords in plaintext. If you do not trust your
-- server please see http://prosody.im/doc/modules/mod_auth_internal_hashed
-- for information about using the hashed backend.
authentication = "cyrus"
cyrus_application_name = "xmpp"
-- Select the storage backend to use. By default Prosody uses flat files
-- in its configured data directory, but it also supports more backends
-- through modules. An "sql" backend is included by default, but requires
-- additional dependencies. See http://prosody.im/doc/storage for more info.
--storage = "sql" -- Default is "internal" (Debian: "sql" requires one of the
-- lua-dbi-sqlite3, lua-dbi-mysql or lua-dbi-postgresql packages to work)
-- For the "sql" backend, you can uncomment *one* of the below to configure:
--sql = { driver = "SQLite3", database = "prosody.sqlite" } -- Default. 'database' is the filename.
--sql = { driver = "MySQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
--sql = { driver = "PostgreSQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
-- Logging configuration
-- For advanced logging see http://prosody.im/doc/logging
--
-- Debian:
-- Logs info and higher to /var/log
-- Logs errors to syslog also
log = {
-- Log files (change 'info' to 'debug' for debug logs):
info = "/var/log/prosody/prosody.log";
error = "/var/log/prosody/prosody.err";
-- Syslog:
{ levels = { "error" }; to = "syslog"; };
}
----------- Virtual hosts -----------
-- You need to add a VirtualHost entry for each domain you wish Prosody to serve.
-- Settings under each VirtualHost entry apply *only* to that host.
VirtualHost "{{ ldh_prosody_domain }}"
enabled = true
-- Assign this host a certificate for TLS, otherwise it would use the one
-- set in the global section (if any).
-- Note that old-style SSL on port 5223 only supports one certificate, and will always
-- use the global one.
-- ssl = {
-- key = "/etc/prosody/certs/example.com.key";
-- certificate = "/etc/prosody/certs/example.com.crt";
-- }
------ Components ------
-- You can specify components to add hosts that provide special services,
-- like multi-user conferences, and transports.
-- For more information on components, see http://prosody.im/doc/components
---Set up a MUC (multi-user chat) room server on conference.example.com:
--Component "conference.example.com" "muc"
-- Set up a SOCKS5 bytestream proxy for server-proxied file transfers:
--Component "proxy.example.com" "proxy65"
---Set up an external component (default component port is 5347)
--
-- External components allow adding various services, such as gateways/
-- transports to other networks like ICQ, MSN and Yahoo. For more info
-- see: http://prosody.im/doc/components#adding_an_external_component
--
--Component "gateway.example.com"
-- component_secret = "password"
------ Additional config files ------
-- For organizational purposes you may prefer to add VirtualHost and
-- Component definitions in their own config files. This line includes
-- all config files in /etc/prosody/conf.d/
Include "conf.d/*.cfg.lua"
ldap_servers: {{ ldh_prosody_ldap_uri }}
ldap_search_base: {{ ldh_prosody_ldap_base }}
\ No newline at end of file
---
- hosts: localhost
remote_user: root
roles:
- ldh_prosody
\ No newline at end of file
---
# vars file for ldh_prosody
\ No newline at end of file
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment