Daniel,
Note that this (and similar) password solutions in Galaxy is not secure in any
real way (especially if you're dealing with patient data or HIPPA):
The password (hidden or visible in a text field) is still transmitted in
clear-text over the network (unless you're using HTTPS/SSL).
If you
Well, it could be modified to never return a value back to the
interface after being set. Would that be sufficient?
On Mon, Apr 4, 2011 at 11:46 AM, Daniel Schmidt wrote:
> Hello all!
>
> Thanks alot K! Although I have to admit, that it seems too insecure, at
> least for the tool I am currently w
Hello all!
Thanks alot K! Although I have to admit, that it seems too insecure, at
least for the tool I am currently working on. The password field is
needed to connect to a database, which contains (sensitive) patient
data. Revealing the password to someone else by accident when re-running
a
Hi Daniel,
I have attached a patch that does this below. You can use it by
setting However the security is lacking as you
can see the string when you try to re-run the job and view source. Is
this sufficient for your purposes?
Thanks,
K
On Sat, Apr 2, 2011 at 11:01 AM, Daniel Schmidt wrote:
>
Hi all!
Is there any way to use password input fields ("type="password"...") with tools? A tools XML definition file only seems
to support text and textarea fields. I already tried setting a tools
parameter type to "password", which unfortunately results in an "Unknown
tool parameter type 'pas
