Re: [galaxy-dev] Bug: Toolbox filters not applied in workflows

2013-12-18 Thread John Chilton
Ahh... missed that. Sorry (and thanks for putting together the page :) ). It seems like we are on the same page - I have created a Trello card for 'stronger' toolbox filters. https://trello.com/c/Sg8D2PBj It occurs to me there may another way to accomplish admin tool functionality - and in an

[galaxy-dev] Bug: Toolbox filters not applied in workflows

2013-12-17 Thread Eric Rasche
I'm running the stable copy of galaxy and noticed that some custom, administrative tools (and otherwise tools which should be restricted in access due to licensing/etc.) were showing up in normal user's toolboxes inside the workflow editor. I feel that this is a bug, as the tool filters should be

Re: [galaxy-dev] Bug: Toolbox filters not applied in workflows

2013-12-17 Thread Dannon Baker
This sounds like a bug; the primary toolbox and workflow editor toolbox should reflect the same set of tools (exception being workflow-specific control steps, etc). I've created a trello card to track this issue here: https://trello.com/c/3TxFHkYR That said, do note the warning on the dynamic

Re: [galaxy-dev] Bug: Toolbox filters not applied in workflows

2013-12-17 Thread Eric Rasche
Okay, thanks for confirming and creating the card. Yes...it's unfortunate that tool filters will not block tools entirely, but this will get it out of the users' view in one more place. On 12/17/2013 05:39 PM, Dannon Baker wrote: This sounds like a bug; the primary toolbox and workflow editor

Re: [galaxy-dev] Bug: Toolbox filters not applied in workflows

2013-12-17 Thread John Chilton
Agreed with Dannon, it is a bug that they are showing up in the workflow editor but in general toolbox filters are not meant as a security mechanism. You can block access to running specific tools (filtered or not) using dynamic job destinations. (Under dynamic job destinations documentation (

Re: [galaxy-dev] Bug: Toolbox filters not applied in workflows

2013-12-17 Thread Eric Rasche
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John, I've been using the dynamic jobs and they've been working beautifully! (For context, I wrote the initial revision of the Access Control page based off of my readings and experiences setting it up in galaxy). I, for one, would be in favour of