Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Changes of displayname from auth providers are not reflected in synapse #4708

Open
tgurr opened this issue Feb 21, 2019 · 3 comments
Open

Changes of displayname from auth providers are not reflected in synapse #4708

tgurr opened this issue Feb 21, 2019 · 3 comments
Labels
S-Minor Blocks non-critical functionality, workarounds exist. T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. Z-Help-Wanted We know exactly how to fix this issue, and would be grateful for any contribution

Comments

@tgurr
Copy link

tgurr commented Feb 21, 2019

Description:

I'm using mxisd with matrix-synapse-rest-auth as password provider to sync users from LDAP/AD.

in mxisd.yaml I have:

ldap:
  enabled: true
  connection:
    host: 'xxx'
    port: 389
    bindDn: 'CN=xxx,OU=xxx,DC=xxx,DC=xxx'
    bindPassword: 'xxx'
    baseDNs:
      - 'OU=xxx,DC=xxx,DC=xxx'
  attribute:
    name: 'cn'

and in homserver.yaml

password_providers:
  - module: "rest_auth_provider.RestAuthProvider"
    config:
      endpoint: "http://localhost:8090"
      policy:
        registration:
          profile:
            name: true
        login:
          profile:
            name: true

When logging in with riot-web I can see the name correctly changing on every login in the top left corner whether I set the name: attribute in myisd.yaml to either 'cn' or 'displayName'.

Also curl https://matrix.domain.local/_matrix/client/r0/profile/%40matrixid%3Adomain.local shows the correct "displayname".

However in the riot-web/matrix profile the "Display Name" is not applied and/or changing accordingly, so in the rooms I already joined I still appear with the matrixid:server.xxx instead of the correct name: transferred by mxisd via LDAP.

In our organization it's quite common for names to change, e.g. because of marriage and thus it would be nice to have an option for synapse to force syncing the displayname to all rooms so users don't need to worry about, don't need to be instructed about and more importantly not making a support request about their old name still being shown.

For reference: kamax-matrix/matrix-synapse-rest-password-provider#6

@richvdh richvdh changed the title Option to force syncing of (changed) displayname across rooms Changes of displayname from auth providers are not reflected in synapse Feb 22, 2019
@neilisfragile neilisfragile added z-p2 (Deprecated Label) z-bug (Deprecated Label) labels Feb 26, 2019
@dklimpel
Copy link
Contributor

dklimpel commented Feb 4, 2020

see also: #6572 and #7023

@n3rdybyn47ur3
Copy link

Anything new?
We had to downgrade our server to synapse 1.18 because the rest auth provider seems to stop working with the following versions. After that we noticed that displayNames dont change correctly (as mentioned above). Maybe the case in newer versions too, but we had no reason to test it. Since we have to deal with a lot of name changes, this is an absolute requirement and an release stopper.

@clokep
Copy link
Member

clokep commented Oct 5, 2020

I don't believe this has ever been supported in Synapse, it probably wouldn't be too terrible, but would require adding a new API method and then updating the auth providers to call it.

@clokep clokep added the Z-Help-Wanted We know exactly how to fix this issue, and would be grateful for any contribution label Oct 5, 2020
@erikjohnston erikjohnston added S-Minor Blocks non-critical functionality, workarounds exist. T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. and removed z-bug (Deprecated Label) z-p2 (Deprecated Label) labels Nov 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
S-Minor Blocks non-critical functionality, workarounds exist. T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. Z-Help-Wanted We know exactly how to fix this issue, and would be grateful for any contribution
Projects
None yet
Development

No branches or pull requests

6 participants