Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Changes in 1.25.0

    Matrix (Synapse/Element)
    3
    12
    376
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • yusf
      yusf last edited by

      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.

      M 1 Reply Last reply Reply Quote 0
      • M
        msbt App Dev @yusf last edited by

        @yusf you can probably disable it via https://github.com/matrix-org/synapse/blob/c659e610b5ffc592ace0588884829a158c5a6d77/docs/sample_config.yaml#L1831

        yusf 1 Reply Last reply Reply Quote 1
        • yusf
          yusf @msbt last edited by

          @msbt Cool, thank you. I'm thinking it should even be disabled by default for the Cloudron Matrix package?

          girish 1 Reply Last reply Reply Quote 0
          • girish
            girish Staff @yusf last edited by

            @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.

            yusf 1 Reply Last reply Reply Quote 0
            • yusf
              yusf @girish last edited by

              @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 1 Reply Last reply Reply Quote 0
              • yusf
                yusf last edited by

                When trying to upgrade the Matrix app:

                1b31cab0-5268-4807-849d-e6670297fb07-bild.png

                What's going on here?

                girish 1 Reply Last reply Reply Quote 0
                • girish
                  girish Staff @yusf last edited by

                  @yusf Not sure. Can you give me screenshot of the app's update section ? What is the version number listed there?

                  yusf 1 Reply Last reply Reply Quote 0
                  • yusf
                    yusf @girish last edited by yusf

                    @girish This is the one:

                    🚫

                    girish 1 Reply Last reply Reply Quote 0
                    • girish
                      girish Staff @yusf last edited by

                      @yusf No, I mean in the Updates view, there is the current package version, last updated, package id etc.

                      yusf 1 Reply Last reply Reply Quote 0
                      • yusf
                        yusf @girish last edited by

                        @girish Sorry, here it is:

                        58605dd2-b1d7-43ac-b2e9-074ac36196d6-bild.png

                        girish 1 Reply Last reply Reply Quote 0
                        • girish
                          girish Staff @yusf last edited by girish

                          @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?

                          1 Reply Last reply Reply Quote 1
                          • yusf
                            yusf @yusf last edited by

                            @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!

                            1 Reply Last reply Reply Quote 1
                            • First post
                              Last post
                            Powered by NodeBB