This use case isn't really addressed by Galaxy currently.
There is not a generic way of doing grabbing the users credentials
like this or producing URLs from inside the tool. This depends on a
lot of different things - how Galaxy's proxy is configured, etc... so
in many (all?) cases Galaxy would not be able to fetch the users raw
credentials. Your best bet is going to be to use the Galaxy's API -
tools can fetch a user's API key and you can use Galaxy's API to build
a URL that includes this key.
Your users will all need API keys set to use the tool. There have been
some other galaxy-dev discussions about using the API from tools -
In general I would discourage this because it is difficult to do in a
generic way - for instance there is no way for the tool to accurately
determine what the URL of Galaxy should be - but it should be possible
to tailor something to your setup if absolutely needed.
If you are really keen to use the Galaxy API to do this and you
understand the limitations - we can try to work through the exact
If it is at all possible to send the data to the web service instead
of sending a reference - the genomespace exporter
might be a good example of how to do this in a more generic fashion.
On Tue, Apr 29, 2014 at 11:16 AM, Dmitry <redmitry(a)list.ru> wrote:
Is there any way to provide a protected resource link to the external
My tool is supposed to call a Web service via SSL which should access to the
In ideal it would be something like
The Web service then downloads the resource and do the computation.
Since user is already provided the login to galaxy, I do not want to ask the
password again on a tool page.
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: