User cannot modify their profile info or picture
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
One user cannot update his profile information. In fact, when this user watches their own profile it looks like they are watching the profile of another user.
When the user tries to change their profile picture, the operation fails and the following appears in the atlassian-confluence.log:
1
2
3
4
5
6
7
8
9
10
11
java.lang.IllegalArgumentException: Profile picture belongs to a different user. Needed user: EmbeddedCrowdUser{name='username', displayName='User Name', directoryId=123456} attachment belongs to username
at com.atlassian.confluence.user.DefaultUserAccessor.setUserProfilePicture(DefaultUserAccessor.java:726)
at sun.reflect.GeneratedMethodAccessor12011.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.atlassian.spring.interceptors.SpringProfilingInterceptor.invoke(SpringProfilingInterceptor.java:16)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
...
Diagnosis
Check that the username in the cwd_user table fully matches the one in the entry for the USERINFO of that particular user in the content table. Be aware that MySQL may trim spaces at the end of the fields before doing comparisons (i.e., ... where username = 'peter' will match username 'peter ').
Cause
This is caused by an extra space at the end of the username field in the content table for the entry of the user's USERINFO.
Solution
Resolution
Remove the extra spaces from the username for the USERINFO in the
contenttable. Remember to take a backup of your database before applying the changes.1 2 3 4 5SELECT CONTENTID FROM CONTENT WHERE USERNAME = '<username>' AND CONTENTTYPE = 'USERINFO'; UPDATE CONTENT SET USERNAME='<username>' WHERE CONTENTID = <content id for the USERINFO>;Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
Was this helpful?