majic-ansible-roles Changeset

Changeset - 54e3820a872e

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Branko Majic (branko) - 10 days ago 2024-09-09 15:03:53
branko@majic.rs

MAR-218: Update to non-deprecated ldap_attrs module in usage instructions.

1 file changed with 6 insertions and 5 deletions:

docs/usage.rst

0 comments (0 inline, 0 general)

docs/usage.rst

➞

Show inline comments

@@ @@ -937,29 +937,29 @@ role. @@
 . Create the keys and certificates for SMTP/IMAP services based on the templates::
         certtool --sec-param normal --generate-privkey --outfile ~/mysite/tls/comms.example.com_smtp.key
         certtool --generate-certificate --load-ca-privkey ~/mysite/tls/ca.key --load-ca-certificate ~/mysite/tls/ca.pem --template ~/mysite/tls/comms.example.com_smtp.cfg --load-privkey ~/mysite/tls/comms.example.com_smtp.key --outfile ~/mysite/tls/comms.example.com_smtp.pem
         certtool --sec-param normal --generate-privkey --outfile ~/mysite/tls/comms.example.com_imap.key
         certtool --generate-certificate --load-ca-privkey ~/mysite/tls/ca.key --load-ca-certificate ~/mysite/tls/ca.pem --template ~/mysite/tls/comms.example.com_imap.cfg --load-privkey ~/mysite/tls/comms.example.com_imap.key --outfile ~/mysite/tls/comms.example.com_imap.pem
 . Configuration and TLS keys have ben set-up, so it is time to apply the changes::
      workon mysite && ansible-playbook playbooks/site.yml
 . Let's add the two users to the mail group (otherwise, the mail
-   server will ignore them). We'll use the ``ldap_attr`` module
+   server will ignore them). We'll use the ``ldap_attrs`` module
    directly to make our life a bit easier::
      workon mysite && ansible --become -m ldap_attr -a "dn=cn=mail,ou=groups,dc=example,dc=com state=present name=uniqueMember values=uid=johndoe,ou=people,dc=example,dc=com" communications
      workon mysite && ansible --become -m ldap_attr -a "dn=cn=mail,ou=groups,dc=example,dc=com state=present name=uniqueMember values=uid=janedoe,ou=people,dc=example,dc=com" communications
      workon mysite && ansible --become -m ldap_attrs -a '{"dn": "cn=mail,ou=groups,dc=example,dc=com", "state": "present", "attributes": {"uniqueMember": "uid=johndoe,ou=people,dc=example,dc=com"}}' communications
      workon mysite && ansible --become -m ldap_attrs -a '{"dn": "cn=mail,ou=groups,dc=example,dc=com", "state": "present", "attributes": {"uniqueMember": "uid=janedoe,ou=people,dc=example,dc=com"}}' communications
 . If no errors have been reported, at this point you should have two mail
    accounts - ``john.doe@example.com``, with password ``johndoe``, and
    ``jane.doe@example.com``, with password ``janedoe``. In this particular
    set-up, the mail addresses are used as usernames. If you want to test it out,
    simply install ``swaks`` on your Ansible machine, and run something along the
    lines of
    ::
      swaks --to john.doe@example.com --server comms.example.com
      swaks --to jane.doe@example.com --server comms.example.com
@@ @@ -1178,26 +1178,27 @@ role. @@
    that we still haven't added any users to the new LDAP group called
    "xmpp". So let us correct this in similar way as we did for the
    mail server. Since we have the user entries already, no need to
    recreate them here. We will just update the group membership
    instead.
    .. warning::
       Same warning applies here as for mail server role for managing the
       user/group entries! Scroll up and re-read it if you missed it!
    ::
       workon mysite && ansible --become -m ldap_attr -a "dn=cn=xmpp,ou=groups,dc=example,dc=com state=present name=uniqueMember values=uid=johndoe,ou=people,dc=example,dc=com" communications
       workon mysite && ansible --become -m ldap_attr -a "dn=cn=xmpp,ou=groups,dc=example,dc=com state=present name=uniqueMember values=uid=janedoe,ou=people,dc=example,dc=com" communications
      workon mysite && ansible --become -m ldap_attrs -a '{"dn": "cn=xmpp,ou=groups,dc=example,dc=com", "state": "present", "attributes": {"uniqueMember": "uid=johndoe,ou=people,dc=example,dc=com"}}' communications
      workon mysite && ansible --become -m ldap_attrs -a '{"dn": "cn=xmpp,ou=groups,dc=example,dc=com", "state": "present", "attributes": {"uniqueMember": "uid=janedoe,ou=people,dc=example,dc=com"}}' communications
 . If no errors have been reported, at this point you should have two users
    capable of using the XMPP service - one with username
    ``john.doe@example.com`` and one with username ``jane.doe@example.com``. Same
    passwords are used as for when you were creating the two users for mail
    server. For testing you can turn to your favourite XMPP client (I don't know
    of any quick CLI-based tools to test the XMPP server functionality,
    unfortunately, but you could try using `mcabber <https://mcabber.com/>`_).
 Taking a step back - preparing for web server

0 comments (0 inline, 0 general)