[Bug]: API unable to set users avatar

[AdamKearn]

Snipe-IT Version

v8.3.6 - build 20551

PHP Version

8.2.29

Composer Version

2.8.12

MySQL/MariaDB version

Ver 15.1 Distrib 10.11.14-MariaDB

How did you install Snipe-IT?

Git install

Is this a fresh install or an upgrade?

Fresh install

What happened?

When calling the API (PATCH request)

$body=@{}
$body.Add("avatar", "$($staffMember.employee_num).png")

Invoke-WebRequest -UseBasicParsing -Uri "${SNIPE_ENDPOINT}/users/1" -Method PATCH -Headers $snipe_headers -ContentType 'application/json' -Body ($body | ConvertTo-Json)

This returns the following repsonce:

{"status":"error","messages":{"avatar":["The avatar field must be a file of type: png, gif, jpg, jpeg, svg, bmp, svg+xml, webp, avif."]},"payload":null}

I'm currently syncing my users images from 365 using another PowerShell script into the /public/avatars folder.
When typing the employee_num.png into the database manually, it will work... is there any reason why this would not be an accepted value?

I've even tried doing the full HTTP URL of the image too.

What browsers are you seeing the problem on?

Microsoft Edge

Can you reproduce this on the public demo?

N/A

Do you have full multiple company support enabled?

Yes

If you have full multiple company support enabled, do you have location scoping to company enabled?

Yes

Application log output

Browser console output

Common Issues

• I have searched this repo for existing issues related to my issue (including closed issues)
• My APP_URL is set correctly in my .env file (including http or https and no trailing slash)
• I have searched the official Snipe-IT documentation and have checked the Common Issues documentation (where applicable)
• I have run database migrations (where applicable).
• I have attached screenshots and/or videos of the issue (where applicable)

Code of Conduct

• I agree to follow this project's Code of Conduct

[snipe]

Hi there - that PATCH request is expecting a base64 or file input, not a string IIRC. It uses the ImageUploadRequest.

[AdamKearn]

Thanks for the response.

Is there no other way other than including the file within the database? I'm going to be syncing a few thousand users and didn't want to clog the DB up with files if possible.

Thanks in advance - I'm loving this product you guys provide.

[snipe]

We don't actually store files in the DB, if that's any relief. We process it, store it on the fileserver, and then generate the filename and store that on the server, via this file:

https://github.com/grokability/snipe-it/blob/master/app/Http/Requests/ImageUploadRequest.php

We could possibly add some kind of override in there that takes just a string and doesn't try to validate it as a binary file. We've avoided doing that in the past because people end up with broken images if they forget to manually move the images to that directory.

GitHub

snipe-it/app/Http/Requests/ImageUploadRequest.php at master · grokability/snipe-it

A free open source IT asset/license management system - grokability/snipe-it

[snipe]

If all of your employees have employee numbers, you could also try this via mysql directly AFTER YOU RUN A BACKUP JUST IN CASE.

UPDATE users SET avatar = CONCAT(employee_num,'.png') WHERE employee_num!='' deleted_at IS NULL;

[AdamKearn]

Ahh thanks for explaining that I assumed it would keep the base64 encoded string in the database.

I might do it that way then. 😀

Yeah my fallback plan also was just like you suggested doing with the employee number joined with the file extension suffix.

Thanks for your advice on this. I'll close this issue for now.

Thank you for your time.