-
-
Notifications
You must be signed in to change notification settings - Fork 856
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
basic auth broken in jirashell #66
Comments
Created pull #67 to fix this, but my github fu to auto-link the two failed |
milo-minderbinder
added a commit
to milo-minderbinder/jira
that referenced
this issue
Jul 15, 2015
…ycontribs#66, and tweaks fix from d585674. The oauth_dance and print_tokens options specified in jirashell.ini configuration file are now correctly parsed as boolean values and OAuth with pre-authenticated access_token and access_token_secret (skipping oauth_dance) is fixed. OAuth options are now minimally validated for completeness, so pycontribs#66 is fixed, allowing for basic_auth without causing issue pycontribs#102 as the merged commit d585674 did previously.
ssbarnea
added a commit
that referenced
this issue
Nov 21, 2016
Fix html_parser import from six.moves.
ssbarnea
pushed a commit
that referenced
this issue
Nov 21, 2016
…rom d585674. The oauth_dance and print_tokens options specified in jirashell.ini configuration file are now correctly parsed as boolean values and OAuth with pre-authenticated access_token and access_token_secret (skipping oauth_dance) is fixed. OAuth options are now minimally validated for completeness, so #66 is fixed, allowing for basic_auth without causing issue #102 as the merged commit d585674 did previously.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
oauth is never None because jirashell.process_config always creates an object, which means that the basic_auth section is now unreachable, as the else section after it.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: