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

@@ @@ -943,17 +943,17 @@ role. @@
 . 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
@@ @@ -1184,14 +1184,15 @@ role. @@
    .. 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

0 comments (0 inline, 0 general)