Drastically changed around how encryption from the user form is done. Most of these changes are centered around the state change of going from encrypted to not or not encrypted to encrypted. If you are going from ‘not’ to ‘encrypted’ then the password will be automatically encrypted. If you are going from ‘encrypted’ to ‘not’ then the validate function will throw an error and you’ll need to re-enter a password (it doesn’t have to match what was there before). I chose this option as a middle road between security and user ease of use. Note: if the user just turns off AES after they had encrypted their API credentials then they are somewhat screwed (it will just send/show the encrypted fields as their encrypted form which will cause a login failure.)