Password field in site properties

By Ricardo Pisco on 23 Feb
Service Center should have the possibility to set site properties as passwords this way the value wasn’t shown.
 
Most of the times we have to put passwords in a site property and there’s no way to hide the value.Service Center should have the possibility to set site properties as passwords this way the value wasn’t shown.
 
Most of the times we have to put passwords in a site property and there’s no way to hide the value.
J.24 Feb
isn't this proposed before?
Hi Ricardo,

 Let me suggest a workaround to your issue which I often see as a better practice:

    1. Create an Entity to store your password(s); this entity will have only 1 record;

    2. Use Forge's CryptoAPI  to encrypt the password in the database and later on to decrypt it as well;

    3. Keep you encryption key (and salt) in another place that is easy to fetch for later use with CryptoAPI in encryption/decryption operations, but also making it difficult for anyone to know about it and trying it out. I don't see an issue in using it as a site property, but it may depend on the sensitivity of your information and who can have access to it in your environment.

 Regards,
 Pedro
Hi Pedro,
This idea would be very useful, to avoid the scenario proposed by you, it would be more straight foward.
Nevertheless, this is smilar to the following idea:
http://www.outsystems.com/ideas/902/cyphered-site-properties
Hi Daniel,
 
The idea you suggested is almost the same thing, but in most of the projects I don’t need the password encrypted I just need to hide the value from the user.
 
I’m talking about something with the behavior of the password widget in Service Studio.