Validation always fails on encrypted custom fields

[fabricat]

Please confirm you have done the following before posting your bug report:

• I have enabled debug mode
• I have read checked the Common Issues page

Describe the bug
Validation always fail on custom fields that are encrypted on database.
I have tested using the NUMERIC and CUSTOM REGEX formats: both are failing (maybe also other formats are affected).

Also an empty value is not accepted.

To Reproduce
Steps to reproduce the behavior:

1. go to 'Manage Custom Fields'
2. click on the 'New Custom Field' button
3. set 'test' as Field Name and 'Text Box' as Field Element
4. choose NUMERIC as Format (or any other format but ANY)
5. enable the Encrypt the value of this field in the database option
6. click on 'Save'
7. add the new field to an existing Fieldset (or create one ad-hoc) - do not flag it as 'Required'
8. make sure the Fieldset is applied to some Asset Model (so the 'test' field is applied)
9. create a new asset of a model matching the above Fieldset
10. write '123' on the 'test' field value (or any other number, or leave it empty)
11. fill in other required fields
12. click 'Save'
13. see the error The test 3 must be a number.

Expected behavior
The value for the 'test' custom field should be accepted as valid.
The same should happen when no value is provided.

Screenshots
Validation fails on the 'test' field (encrypted), while is successful on the other non-encrypted field.
Both fields are configured as NUMERIC format.

Server (please complete the following information):

• Snipe-IT Version: 5.1.5 (docker official image)

Desktop (please complete the following information):

• OS: Windows
• Browser: Chrome
• Version: 87

Smartphone (please complete the following information):
n/a

Error Messages

• no errors appear on the phpdebugbar
• no errors appear in browser's error console
• the error is reproducible on the demo: https://snipeitapp.com/demo.
• no entries appear on docker container's logs

Additional context

• Server has been upgraded, but the error was present also on the previous version (5.1.4)
• the server is deployed using the official docker image
• no errors so far
• no manually edited data directly in the database

[snipe]

Hi there - I know this is a pretty old issue, but I wanted to check and see if you ever got this resolved? If so, can you please close the ticket? If not, can you update us on what version of Snipe-IT you're currently using, so we can see if it's still an issue on latest?

:) Thanks!

[fabricat]

Thanks for the update.

I have just re-tested with current version: 6.0.8 (Docker image)
The issue is still there 🙁

The only thing I can do to resolve is using only non-encrypted fields 😅

[dernisonj]

The issue is still present in the current demo version. Does the Custom-Regex run against the data in the field before it is saved to the DB or after it is encrypted?

It would be nice to verify items like BitLocker Recovery keys contain all 48 characters and have them stored securely.

[snipe]

@dernisonj are you seeing this only with regex? I can't reproduce it with NUMERIC. Can you share the regex you're using so we can try to test?

[dernisonj]

I have the field currently set as a text box. regex:/^[0-9]{6}-[0-9]{6}-[0-9]{6}-[0-9]{6}-[0-9]{6}-[0-9]{6}-[0-9]{6}-[0-9]{6}$/ I have not tested with other validation methods as I need to validate that it is both numeric and contains 48 characters not including the separator character (-). From: snipe ***@***.***> Sent: Friday, June 6, 2025 15:27 To: grokability/snipe-it ***@***.***> Cc: Jeremy Dernison ***@***.***>; Mention ***@***.***> Subject: [EXTERNAL] Re: [grokability/snipe-it] validation always fails on encrypted custom fields (#9511) [https://avatars.githubusercontent.com/u/197404?s=20&v=4]snipe left a comment (grokability/snipe-it#9511)<#9511 (comment)> @dernisonj<https://github.com/dernisonj> are you seeing this only with regex? I can't reproduce it with NUMERIC. Can you share the regex you're using so we can try to test? - Reply to this email directly, view it on GitHub<#9511 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BRPWIL7DC3B6IH2RYV3FDEL3CHTRFAVCNFSM6AAAAAB6YU3LBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJQGQ2TAMRSGI>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> CONFIDENTIALITY NOTICE: This electronic mail transmission and any accompanying attachments are intended only for the use of the addressee and may contain information that is legally privileged and confidential. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or action taken in reliance on the contents of these documents is strictly prohibited. If you have received this transmission in error, please notify the sender immediately by email and delete the original message.

[snipe]

@dernisonj - thanks - this helps a ton. We'll take a look first thing tomorrow.