Changes in 1.25.0
-
Just read the release notes for Synapse 1.25.0. They include:
The ability for users to pick their own username when using Single Sign-On, right from within Synapse.
This is a red flag for me since I need for the Matrix IDs to strictly map onto the Cloudron usernames. Please disable or opt out of this feature for next release.
-
Just read the release notes for Synapse 1.25.0. They include:
The ability for users to pick their own username when using Single Sign-On, right from within Synapse.
This is a red flag for me since I need for the Matrix IDs to strictly map onto the Cloudron usernames. Please disable or opt out of this feature for next release.
-
@yusf you can probably disable it via https://github.com/matrix-org/synapse/blob/c659e610b5ffc592ace0588884829a158c5a6d77/docs/sample_config.yaml#L1831
-
@msbt Cool, thank you. I'm thinking it should even be disabled by default for the Cloudron Matrix package?
-
@yusf Do you know why the decided to keep this as the default? Generally, we prefer not to change the upstream defaults unless it's privacy related.
@girish They sre apparently changing the default to allowing custom usernames. This is terrible for me but it might also be undesired behavior within the general Cloudron experience.
localpart_template: "{{ user.preferred_username }}"The above setting activated is responsible for retaining the previous behavior, iirc.
-
@yusf Not sure. Can you give me screenshot of the app's update section ? What is the version number listed there?
-
@yusf No, I mean in the Updates view, there is the current package version, last updated, package id etc.
-
@yusf Looks like you are already on the latest release. I think if "refresh" the browser, the update available will probably go away. This bug is fixed in next release. If it doesn't, can you check if it goes away if you go to Settings -> Check For Updates?
-
@girish They sre apparently changing the default to allowing custom usernames. This is terrible for me but it might also be undesired behavior within the general Cloudron experience.
localpart_template: "{{ user.preferred_username }}"The above setting activated is responsible for retaining the previous behavior, iirc.
@yusf said in Changes in 1.25.0:
@girish They sre apparently changing the default to allowing custom usernames. This is terrible for me but it might also be undesired behavior within the general Cloudron experience.
localpart_template: "{{ user.preferred_username }}"The above setting activated is responsible for retaining the previous behavior, iirc.
It seems that I've cried wolf since when setting up a new test user, no prompt was given to med when signing it in to the LDAP-enabled Matrix server with Element. Good!
