-
Notifications
You must be signed in to change notification settings - Fork 991
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support different authentication methods #1
Conversation
Initial modules: - ActiveDirectory (ldap) - LocalDB (fall back to galaxy users) - AlwaysAccept (whitelist) - AlwaysReject (blacklist) Sysadmin documentation at: https://docs.google.com/document/d/1CJp_m3vW7QKtAyBTMbE1MLgV6FAMuG3VO4HR-wHPkGk Testing documentation at: https://docs.google.com/document/d/1Cocx6Rt3eqPdm8IjOKYAR4RaY-9P2iFNXCt3AYg3PlA
Added a config/customauth_conf.xml.sample file containing only the normal Galaxy database authentication method. Removed enable_customauth config option.
A bit more previous discussion on this PR can be found at galaxyproject/galaxy-beta1#4 |
Here is how I would rip out yapsy -
(E.g. https://github.com/galaxyproject/galaxy/blob/d1cd4ab4d28c72f365852b75e2f2026c6b76ebbd/lib/galaxy/workflow/scheduling_manager.py
|
@jmchilton This WIP commit nsoranzo@b55edfe should address your first 3 points. |
This is an automated message. Thanks for your contribution, a Trello card to track this issue has been created. Apply this patch for testing. |
Picked up where @nsoranzo left off and merged directly - let me know if I broke anything. I made a lot of cosmetic changes to the code to make it mesh with Galaxy standards but the end-user usage should remain largely unchanged - no difference for deployers and plugin developers need to stick a Many thanks to @nsoranzo and @andrewjrobinson and the people who reviewed the pull request in its various forms! |
Thank you @jmchilton for driving this and @nsoranzo for the contributions. 👍 👍 |
Thanks @nsoranzo and @jmchilton for your help here and others for your reviews. I have tested the changes against the tests I used during development and found one bug with the auto-registration. I have fixed this issue and retested. The fix is currently sitting in my fork of this repo (https://github.com/andrewjrobinson/galaxy dev branch). Should I submit another pull request or do something else to get it merged? |
Thanks @jmchilton for finishing and polishing it! I posted a comment on commit 9fd6685 for you. @andrewjrobinson I think a PR would be ideal! |
@andrewjrobinson Yep, sending another PR is the best way to incorporate a bugfix. |
Some possible follow up tasks here - https://trello.com/c/sxz9SM2R if anyone is bored. |
run tests from outer directories
Fix import problem with msa.py.
Merge latest dev, resolve conflicts.
add titles to explan TS mercurial browser links
Simplify strict_min strict_max logic.
Code cleanup. from @nsoranzo
Refactor reports styling out into its own less file.
Fix failing tests for 238d908.
Convert to RST, fix image references.
Enhance the Merge Collections Tool
Add fastq(*).bz2 datatypes and converters
Swap two more spots initializing TagManagers to new session
Small javascript fixes for askomics IE integration
Update from Galaxyproject repo
Need to set default HOME/TMP before env_setup_commands
Test dumping multiple="false" data_column param as json
Add tool test for metadata_in_range
Move object store test upload test cases to test/integration/objectstore
Make sure cached images are properly sorted by build build_number and…
Add select and <filter> example
Pull John's updates into my branch
This is a revised version of BitBucket PR #555.
Initial modules:
Sysadmin documentation at: https://docs.google.com/document/d/1CJp_m3vW7QKtAyBTMbE1MLgV6FAMuG3VO4HR-wHPkGk
Problems:
Tested and approved by original author @andrewjrobinson .