Hi @fsmit,
Thank you for your message and for using the Encode/Decode/ Encrypt/Decrypt Plugin for Bubble.
I’ve verified with the dev team and they confirmed that this plugin was designed for encoding/decoding text by using different encryption/decryption methods.
I’m afraid your use case can’t be achieved.
It is generally not possible to search through encrypted text values by their original text in a database, including a Bubble database.
Encryption transforms the original text into a format that is unreadable and should not bear any resemblance to the original text. This is a fundamental property of strong encryption algorithms like AES. The process is designed to ensure that without the proper key, there is no feasible way to derive any information about the original text from the encrypted text.
If you have encrypted a piece of data with AES, you should indeed be able to decrypt it using any tool or library that implements AES, provided you have the correct key, and you are using the same encryption parameters.
However, there are several factors you need to ensure match between the encryption and decryption processes:
-
Key: You must use the exact same key for decryption that was used for encryption.
-
Cipher Mode: AES can operate in different modes, such as ECB (Electronic Codebook), CBC (Cipher Block Chaining), CFB (Cipher Feedback), OFB (Output Feedback), etc. You need to use the same mode for decryption that was used for encryption.
-
Initialization Vector (IV): For modes like CBC, an Initialization Vector is used as an additional input along with the key. The IV does not need to be secret, but it should be random and unique for each encryption. If an IV was used during encryption, you need to use the same IV for decryption.
-
Padding: AES operates on blocks of data, and the data to be encrypted needs to be a multiple of the block size. Padding is used to fill up the last block if the data is not a multiple of the block size. Common padding schemes include PKCS7, zero padding, etc. You need to use the same padding scheme for decryption that was used for encryption.
-
Key Size: AES supports different key sizes, typically 128, 192, or 256 bits. You need to use the same key size for decryption that was used for encryption.
-
Encoding: Before and after encryption, the data may be encoded in some way (e.g., base64, hex). You need to ensure that you are properly encoding and decoding your data at each step.
Hope this helps.
Let me know if you have other plugin-related questions.
Take care, 
