Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All custom fields values show "encrypted" in history when they are not #13658

Closed
2 tasks done
squintfox opened this issue Sep 26, 2023 · 7 comments
Closed
2 tasks done
Labels
✋ bug Confirmed bug

Comments

@squintfox
Copy link
Contributor

squintfox commented Sep 26, 2023

Debug mode

Describe the bug

After upgrading from 6.1.2 to 6.2.0, all existing history entries that show custom fields do not show the actual values anymore, they just say the word "encrypted" for both pre and post values. Any new changes to a custom field, do the same. The custom fields were not created as encrypted and the values display correctly in the info page and list views. This happens in the demo, so I used that to reproduce.

Reproduction steps

  1. Go to Asset# 1376559076 in demo.snipeitapp.com.
  2. Edit Asset
  3. Change the value of "CPU"
  4. Save
  5. Go to History
  6. See log entry and values of _snipeit_cpu_4 are shown as encrypted.

Expected behavior

Original and new values should be shown in cleartext

Screenshots

Screenshot 2023-09-26 152429

Screenshot 2023-09-26 152501

Snipe-IT Version

6.2.0

Operating System

Unknown

Web Server

Unknown

PHP Version

8.1.21

Operating System

No response

Browser

No response

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

@welcome
Copy link

welcome bot commented Sep 26, 2023

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

@TonyTheDarkLord
Copy link

Same here! 😕

image

@snipe
Copy link
Owner

snipe commented Sep 28, 2023

Thanks for reporting this - I'm looking at it now. Good news is that the data itself is intact - we're just displaying it incorrectly. I should have a fix out for you shortly.

@snipe snipe added the ✋ bug Confirmed bug label Sep 28, 2023
@snipe
Copy link
Owner

snipe commented Sep 28, 2023

Okay, I think I've got this sorted. PR incoming.

Screenshot 2023-09-28 at 2 32 14 AM

@squintfox
Copy link
Contributor Author

@snipe I pulled the new version and it's working great. Thank you so much.

@snipe
Copy link
Owner

snipe commented Sep 28, 2023

@squintfox no problem - sorry for the glitch!

@TonyTheDarkLord
Copy link

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✋ bug Confirmed bug
Projects
None yet
Development

No branches or pull requests

3 participants