CiviCRM Community Forums (archive)

Since this is an infrequently used admin-only form, AND processor passwords are often quite complex, AND debugging problems based on incorrect password input could potentially be a nightmare - I'm not convinced that this is a good idea.

You might be able to use the smarty plugin crmReplace in your template to change the input type from "text" to "password".

Of course, if we get a lot of folks agreeing that this field SHOULD be masked, I'm open to thinking differently about this :-)

I realize that I'm picking up on a an old threat... but we've experienced this problem too.

I don't think masking using the password input type is the right answer, both for the reasons Dave gives and because anyone with the right browser plugin can unmask these passwords.

I think a better option would be to define a privilege called Administer Payment Processors, so we can give people admin access without giving them access to this piece of sensitive data.

What do you think?

Maybe we can do both - new permission for admin payment processor, and some encryptiong of the stored value with the site key (the IPN code would need to decrypt before sending to the processor of course). ?