Cannot visit Strongbox::Lock - error about strongbox HOT 4 CLOSED

Strongbox has tests for more than one field which pass under 3.1, so my guess is that's not the root of the problem. "Cannot visit" appears to be raised when a string is expected and instead an object is found. Strongbox turns the encrypted fields into objects, so this seems likely. Do you have any validations on those fields?

from strongbox.

I've solved the problem.

I had this line in my user model.

 validates_uniqueness_of :phone_number, scope: [:username]

I used the validation above before I changed the type of the username column from string to binary.

In other words; this should work.

 validates_uniqueness_of :phone_number

@spikex Any idea why this is happening?

from strongbox.

It happens because when the scope feature of validates_uniqueness_of ends up with the Lock object when it was expecting the string value of the column. You could argue that this is a bug in validates_uniqueness_of, that it should call to_s to make sure it has a string.

But, it's never going to work in Stongbox; even if you had the username for the scope, given that a string is never encrypted the same way twice, that username can't be matched against the already encrypted ones in the database.

from strongbox.

That explains a lot, thanks!

from strongbox.