Re: [Myexperiment-discuss] strategies for excluding username/password from logbook?

[James Howison]

On Jun 18, 2008, at 4:31 AM, Stian Soiland-Reyes wrote:

> On Sun, Jun 15, 2008 at 3:31 PM, James Howison <address@hidden>  
> wrote:
>
>
>
> > We'd like the user/pass not to show up in the results.
> >
> > Currently I see three options:
> >
> > user/pass as workflow inputs
> > user/pass as default values
> > user/pass as "ask for value" pop-up results
> >
> > But all these show up in the logbook results.
>
> Hi!
>
> Taverna 2 will come with support for a security agent, which would be
> able to provide username/password (and similar authorisation
> information) "on the side" of the workflow instead of exposing them as
> values.

Sounds good.  So components would be able to get data from the  
security agent when needed?

> However, we're also redoing the logbook for Taverna 2, and the data
> structures are most probably going to look a bit different - for
> instance to properly handle iteration.

Could I follow this discussion on taverna-dev? I've been thinking a  
lot recently about 'typing' input/output variables using Classes  
defined in owl ontologies.

> When would you need this for..?

Last week :)  Of course, I kid.

What I did was arrange services to go through a proxy with a 'fake'  
password.  I can then revoke that password 'locally', without having  
to change our password on the remote services.  This is obviously not  
ideal, it only protects against accidental exposure, so we'd love  
people to be able to use their own user/pass details with the  
workflows when we come to publish, which is by the end of northern  
summer.

What's the timetable for T2, again?

Thanks,
James