From 7a1acbe1016204af65067a3edfa1f84efd653e34 Mon Sep 17 00:00:00 2001 From: Thorsten Eckel Date: Fri, 20 Apr 2018 11:18:31 +0200 Subject: [PATCH] Fixed issue #1642: Incorrect redirect_uri during OAuth2 access token request breaks integrations. --- config/initializers/omniauth.rb | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/config/initializers/omniauth.rb b/config/initializers/omniauth.rb index 0b5491901..24c91e0e5 100644 --- a/config/initializers/omniauth.rb +++ b/config/initializers/omniauth.rb @@ -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' 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')}" +}