Fixed issue #1642: Incorrect redirect_uri during OAuth2 access token request breaks integrations.
This commit is contained in:
parent
5f728f20c3
commit
7a1acbe101
1 changed files with 8 additions and 0 deletions
|
@ -50,3 +50,11 @@ Rails.application.config.middleware.use OmniAuth::Builder do
|
||||||
provider :weibo_database, 'not_change_will_be_set_by_database', 'not_change_will_be_set_by_database'
|
provider :weibo_database, 'not_change_will_be_set_by_database', 'not_change_will_be_set_by_database'
|
||||||
|
|
||||||
end
|
end
|
||||||
|
|
||||||
|
# This fixes issue #1642 and is required for setups in which Zammad is used
|
||||||
|
# with a reverse proxy (like e.g. NGINX) handling the HTTPS stuff.
|
||||||
|
# This leads to the generation of a wrong redirect_uri because Rack detects a
|
||||||
|
# HTTP request which breaks OAuth2.
|
||||||
|
OmniAuth.config.full_host = proc {
|
||||||
|
"#{Setting.get('http_type')}://#{Setting.get('fqdn')}"
|
||||||
|
}
|
||||||
|
|
Loading…
Reference in a new issue