Conversation
gunicorn if auth.api_url config option was not set. NOTE: This issue would only affect deployments using gunicorn which don't have auth.api_url config option set.
arm4b
approved these changes
Oct 31, 2019
Member
arm4b
left a comment
There was a problem hiding this comment.
LGTM,
only missing a respective CHANGELOG record
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request fixes a bug with
POST /auth/v1/tokensAPI endpoint returning internal server error when running under gunicorn withoutauth.api_urlconfig option being set.NOTE: First I couldn't reproduce the issue, but it turns out it only happens when using gunicorn deployment.
When running st2auh directly, the WSGI implementation simply casts all the "None" header values to empty strings, but that's not the case for gunicorn.
Originally reported here - https://forum.stackstorm.com/t/ldap-error-handling-api-call-failed-expected-string-or-buffer/893.