9a9b7383e9
This change is provoked by a few different things: - #54 (Github Pull Request), which rightfully says that we need a way to support ALL mxisd configuration options easily - the upcoming mxisd 1.3.0 release, which drops support for property-style configuration (dot-notation), forcing us to redo the way we generate the configuration file With this, mxisd is much more easily configurable now and much more easily maintaneable by us in the future (no need to introduce additional playbook variables and logic).
1.7 KiB
Adjusting mxisd Identity Server configuration (optional)
By default, this playbook configures an mxisd Identity Server for you.
This server is private by default, potentially at the expense of user discoverability.
Matrix.org lookup forwarding
To ensure maximum discovery, you can make your identity server also forward lookups to the central matrix.org Identity server (at the cost of potentially leaking all your contacts information).
Enabling this is discouraged and you'd better learn more before proceeding.
Enabling matrix.org forwarding can happen with the following configuration:
matrix_mxisd_matrixorg_forwarding_enabled: true
Additional features
What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services.
A few variables can be toggled in this playbook to alter the mxisd configuration that gets generated.
Still, mxisd can do much more. You can refer to the mxisd website for more details and configuration options.
To use a more custom configuration, you can define a matrix_mxisd_configuration_extension_yaml string variable
and put your configuration in it.
To learn more about how to do this, refer to the information about matrix_mxisd_configuration_extension_yaml in the default variables file.
Troubleshooting
If email address validation emails sent by mxisd are not reaching you, you should look into Adjusting email-sending settings.