nextcloud / nextcloud/user_saml
Missing `UserChangedEvent` after setting attributes
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- See avatar is the fallback (initials) of an user but due to missing display name its the userid
- Setup SAML to also populate display name from IdP
- See avatar is still based on initials of user id
Expected behavior
The setting of the display name should emit an UserChangedEvent so that the server will re-generate an avatar.
Actual behaviour
Event is not emitted and thus the old avatar is not replaced.
Server configuration
Nextcloud version: 33
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the SAML configuration path that populates the user's display name, then trace how setting that attribute is handled. Reproduce the fallback-avatar case described in the issue and verify that the display-name update emits UserChangedEvent and causes the avatar to be regenerated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100