v1.4.0-alpha.1
Pre-releaseNotes
This new pre-release paves the way towards v1.4.0 with a big focus in new areas:
- Administration commands/interfaces
- Ability to expire and clean-up pending 3PID invites
- Official support for semi-open server setups vs best effort until now
- Provide control over the remaining Client API endpoints where 3PIDs are involved
Semi-open servers are defined as servers that:
- Allow registration but only with some approval process
- Only allows a specific set of people to create 3PID invites, which can be used to register a new account
- Needs the ability to list and manage pending 3PID invites
IMPORTANT: This release changes the format of the data since previous releases. While this is an automatic upgrade, it also means it is not possible to downgrade to any previous version.
BE SURE TO BACKUP YOUR mxisd DATA FOLDER if you use pre-releases!
Features
The following new features were added:
Administration
It is now possible to administer your mxisd instance directly within your Matrix client, thanks to the Application Service feature of mxisd.
See the Documentation to get started.
3PID invite expiration
One of the main limitation in terms of 3PIDs in Matrix is the inability to cancel or otherwise control in any way pending 3PID invites. If those are not accepted/resolved, they remain in a room forever.
mxisd can now be leveraged to cancel any 3PID invites made through it, either automatically after a configurable period of time, or manually via the admin interface.
See the Documentation to get started.
3PID invite policies
It is now possible to restrict the creation of 3PID invites to a certain set of users on your servers (e.g. Admins or VIPs) using roles returned by the Profile feature of Identity Stores. This would typically be used together with the new Registration feature.
See the Documentation to get started.
Registration
mxisd now offer the possibility to partially control registrations to ensure that provided 3PIDs, if made mandatory at the Homeserver level, are allowed given specific patterns or if matching pending 3PID invite.
See the Documentation to get started.
Identity Service r0.1.0 compliance
mxisd now implements all flows and features of the r0.1.0 spec. Ephemeral keys and ephemeral signing was the last remaining element not supported until now. mxisd is therefore the first 3rd party Identity server to be compliant with the stable Matrix specification.
Version check
mxisd now provides two ways to check for its version:
- At command line, with
--version
- With the API, at
/version
(not under the public/_matrix
to keep the info private)
Changes
- The Application Services feature configuration was changed to support the new features of this release. If you used it prior to v1.4.0, adapt your
mxisd.yaml
as needed. Application Services integration itself is still considered experimental. - The
mxisd.yaml
sample file now talks aboutserver.name
(37ddd0e) - Block a non-public but still under
v1
namespace custom endpoint from New Vector (95ee328) - Various doc improvements (93bd735, c5cea93, 838d79a, 9abdcc1)
- Debian package now has
status
andpriority
- Thanks @joshuaboniface (1587103)
Packages
Platform | Type | Command/Link |
---|---|---|
All | Jar | Download |
Debian | Package | Download |
Docker | Image | docker pull kamax/mxisd:1.4.0-alpha.1 (Repo) |
Checksums
Platform | Type | SHA-256 |
---|---|---|
All | Jar | 9e5d43900e448eb630c6167d58805928358c74d7dc3698738f2e65beb9b0ba87 |
Debian | Package | d150a65fbbe1a9f93de78d1210ab64f0d8771ea721c4a502b886ef606782b213 |