You don’t necessarily need to use the validation widget: you can just model this in your microflow, see this documentation for some best practices.
Thanks for using the Appronto Validator!
A popup message is usually a sign that the validated field is not displayed in your client or the validation is added to the incorrect object and/or attribute. It seems that you are passing in all the right objects (Student and attribute Password if I’m not mistaken.)
I’ve recreated your scenario with associations etc., based on your question and I am not getting the same result; just the correct feedback message under the password field how it suppose to be working.
Can you clarify which Encryption Widget you are talking about?
You’re getting the validation popup because the Encryption widget does not register itself as a validation handler for the password attribute. The custom widget boilerplate has an example of how to implement this. See the widget registering itself for validation feedback here.
Side question: what is the Encryption widget doing? Why can’t you just use a normal input set to “password” mode?