Please excuse any typos -- Sent from my iPhone
On Oct 8, 2015, at 11:35 AM, Eric Rasche <esr(a)tamu.edu> wrote:
The bug fix for this is now in Galaxy's dev branch, and I've opened a PR
to have it in the 15.10 release. This is the patch for your bug if you
need it sooner than the next release (assuming that PR gets merged).
> On 10/07/2015 04:43 PM, Eric Rasche wrote:
> Not from the admin interface right now. I noted this bug just the other
> day and intended to fix it as it applied to us as well.
> Until then, you can easily change the API key manually in the database.
> 2015-10-07 16:20 GMT-05:00 Ryan G <ngsbioinformatics(a)gmail.com
> Hi all - I have external authentication established with our
> enterprise wide LDAP working with Galaxy. I just noticed that I can
> no longer manage API keys for users from the Admin Page -> API
> Keys. I get "Access to Galaxy user controls is disabled. User
> controls are disabled when Galaxy is configured for external
> We basically have a 'nobody' user in Galaxy that populates the Data
> Library with new data from a proprietary system. We were using a
> user's API key (mine) to do this but want to switch over to a daemon
> style user key. In order to do so, I need to generate an API key
> for the dummy user.
> Is there no way to get API keys from the Admin interface with
> external authentication?
> 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:
> Eric Rasche
> Programmer II
> Center for Phage Technology
> Rm 312A, BioBio
> Texas A&M University
> College Station, TX 77843
> esr(a)tamu.edu <mailto:email@example.com>
Center for Phage Technology
Rm 312A, BioBio
Texas A&M University
College Station, TX 77843