Hi everyone. I am using SSO on my forum and avatars are controlled by my website. Until a few days ago, avatar upload/update from the website to the Discource, via API was working. I now get a 422 - Unprocessable Entity error. I’ve tried to debug the issue, did some testing with Postman and I have the same issues. The request I am doing is below (with url, username and api_key removed, of course). Does any of you know if there’s any issue with this portion of Discourse? Thank you in advance. My example: curl --location --request PUT 'https://{{URL}}/u/{{USERNAME}}/preferences/avatar/pick' \ --header 'Api-Key: {{API_KEY}}' \ --header 'Api-Username: system' \ --header 'Content-Type: application/json' \ --data-raw '{ "upload_id": 972, "type": "uploaded" }'

Anyone? Isn’t there anyone that has found the same problem?

This is probably related to the change to the API to do direct uploads to S3?

I think that would interfere with the actual upload, not the assignment of the avatar to the user. I can upload the file without any issue. When I make the call to the API to indicate which file to use as an avatar, that’s where I get the error and that started out of the blue.

I’m trying my luck and boost this one last time. It’s odd that no one has found this. I am sure it’s not a coding issue since it has been working for over a couple of years now.

I think this is due to the discourse connect overrides avatar site setting. [image] Overrides user avatar with value from DiscourseConnect payload. If enabled, users will not be allowed to upload avatars on Discourse. On my local with that unchecked I get a 200 http response when updating the avatar via the api: curl -i -sS -X PUT "http://localhost:4200/u/10614bb2d4eacd328c45/preferences/avatar/pick.json" \ -H "Content-Type: multipart/form-data" \ -H "Api-Key: 6cea489d21282803c446fd2e9d236901c3d186f36079911833db4b57c43c01d5" \ -H "Api-Username: blake.erickson" \ -F "upload_id=57" \ -F "type=uploaded" HTTP/1.1 200 OK And I get a 422 with that setting checked: curl -i -sS -X PUT "http://localhost:4200/u/021ca796a01ad178bc52/preferences/avatar/pick.json" \ -H "Content-Type: multipart/form-data" \ -H "Api-Key: 6cea489d21282803c446fd2e9d236901c3d186f36079911833db4b57c43c01d5" \ -H "Api-Username: blake.erickson" \ -F "upload_id=57" \ -F "type=uploaded" HTTP/1.1 422 Unprocessable Entity

Hi Blake. Thanks for pitching in. Enable or disabling it makes no difference, unfortunately.

I don’t have an answer yet, but just wanted to let you know that this is on my list to look into. I have a sso setup I can test locally, so that our settings match. It seems like we should be respecting that site setting which could be a change someone made recently, but maybe we could add an API override.

Thank you very much, Blake. Please let me know if there’s anything I can help with.

Hi Richard! Thanks for your input. I thought about that as well but it didn’t work. Also, this issue appeared out of the blue. No one changed anything (I am the only admin so there’s no chance someone could have switched any settings), no code changes on the main website, nothing.

בחירת אוואטר משתמש דרך API כבר לא עובד

מפתח

RGJ (Richard - Communiteq) 20 בדצמבר,‏ 2021,‏ 10:32pm 12

Another reason for a 422 from that method can be if the allow_uploaded_avatars setting is false. I bet that’s the issue.

נושא		תגובות	צפיות
Off-site avatar via API? Development rest-api	3	744	28 באוקטובר,‏ 2020
Discourse connect avatar_url isn't working SSO	9	910	29 באוקטובר,‏ 2025
Failing to change avatar using Discourse API Development rest-api	6	702	16 באפריל,‏ 2023
Discourse connect sync_sso avatar update issue SSO rest-api	0	852	11 באוקטובר,‏ 2021
Delete user avatar by API Development rest-api	14	2380	23 ביוני,‏ 2020

בחירת אוואטר משתמש דרך API כבר לא עובד

נושאים קשורים