OAuth 오류 - 오류의 정확한 원인을 파악할 수 없음

제품 지원
1

OAuth 오류가 발생하고 있고, 페이지를 새로고침해야 작동합니다… 오류 로그를 확인했는데, 상세 내용은 다음과 같습니다:::

The image is a screenshot of an error message from a discussion forum, indicating that the software powering the forum encountered an unexpected problem and asking for further information if the issue persists. (Captioned by AI)
The image is a screenshot of an error message from a discussion forum, indicating that the software powering the forum encountered an unexpected problem and asking for further information if the issue persists. (Captioned by AI)1041×138 68.7 KB

Faraday::TimeoutError (Timeout::Error)

아래와 같은 트레이스백 로그 오류가 발생합니다:

activesupport-7.2.2/lib/active_support/broadcast_logger.rb:130:in `block in warn'
activesupport-7.2.2/lib/active_support/broadcast_logger.rb:231:in `block in dispatch'
activesupport-7.2.2/lib/active_support/broadcast_logger.rb:231:in `each'
activesupport-7.2.2/lib/active_support/broadcast_logger.rb:231:in `dispatch'
activesupport-7.2.2/lib/active_support/broadcast_logger.rb:130:in `warn'
/usr/local/lib/ruby/3.3.0/forwardable.rb:240:in `warn'
/var/www/discourse/plugins/discourse-oauth2-basic/lib/oauth2_faraday_formatter.rb:7:in `request'
faraday-2.12.1/lib/faraday/response/logger.rb:22:in `call'
faraday-2.12.1/lib/faraday/rack_builder.rb:152:in `build_response'
faraday-2.12.1/lib/faraday/connection.rb:452:in `run_request'
oauth2-1.4.11/lib/oauth2/client.rb:107:in `request'
oauth2-1.4.11/lib/oauth2/client.rb:177:in `get_token'
oauth2-1.4.11/lib/oauth2/strategy/auth_code.rb:32:in `get_token'
omniauth-oauth2-1.7.3/lib/omniauth/strategies/oauth2.rb:126:in `build_access_token'
omniauth-oauth2-1.7.3/lib/omniauth/strategies/oauth2.rb:91:in `callback_phase'
omniauth-1.9.2/lib/omniauth/strategy.rb:238:in `callback_call'
omniauth-1.9.2/lib/omniauth/strategy.rb:189:in `call!'
omniauth-1.9.2/lib/omniauth/strategy.rb:169:in `call'
omniauth-1.9.2/lib/omniauth/builder.rb:45:in `call'
/var/www/discourse/lib/middleware/omniauth_bypass_middleware.rb:43:in `call'
rack-2.2.10/lib/rack/tempfile_reaper.rb:15:in `call'
rack-2.2.10/lib/rack/conditional_get.rb:27:in `call'
rack-2.2.10/lib/rack/head.rb:12:in `call'
actionpack-7.2.2/lib/action_dispatch/http/permissions_policy.rb:38:in `call'
/var/www/discourse/lib/content_security_policy/middleware.rb:12:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:397:in `call'
/var/www/discourse/lib/middleware/csp_script_nonce_injector.rb:12:in `call'
/var/www/discourse/config/initializers/008-rack-cors.rb:14:in `call'
rack-2.2.10/lib/rack/session/abstract/id.rb:266:in `context'
rack-2.2.10/lib/rack/session/abstract/id.rb:260:in `call'
actionpack-7.2.2/lib/action_dispatch/middleware/cookies.rb:704:in `call'
actionpack-7.2.2/lib/action_dispatch/middleware/callbacks.rb:31:in `block in call'
activesupport-7.2.2/lib/active_support/callbacks.rb:101:in `run_callbacks'
actionpack-7.2.2/lib/action_dispatch/middleware/callbacks.rb:30:in `call'
actionpack-7.2.2/lib/action_dispatch/middleware/debug_exceptions.rb:31:in `call'
actionpack-7.2.2/lib/action_dispatch/middleware/show_exceptions.rb:32:in `call'
logster-2.20.0/lib/logster/middleware/reporter.rb:40:in `call'
railties-7.2.2/lib/rails/rack/logger.rb:41:in `call_app'
railties-7.2.2/lib/rails/rack/logger.rb:29:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:20:in `call'
/var/www/discourse/config/initializers/100-silence_logger.rb:29:in `call'
actionpack-7.2.2/lib/action_dispatch/middleware/request_id.rb:33:in `call'
/var/www/discourse/lib/middleware/enforce_hostname.rb:24:in `call'
rack-2.2.10/lib/rack/method_override.rb:24:in `call'
actionpack-7.2.2/lib/action_dispatch/middleware/executor.rb:16:in `call'
rack-2.2.10/lib/rack/sendfile.rb:110:in `call'
rack-mini-profiler-3.3.1/lib/mini_profiler.rb:191:in `call'
/var/www/discourse/lib/middleware/processing_request.rb:12:in `call'
message_bus-4.3.8/lib/message_bus/rack/middleware.rb:60:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:360:in `call'
actionpack-7.2.2/lib/action_dispatch/middleware/remote_ip.rb:96:in `call'
railties-7.2.2/lib/rails/engine.rb:535:in `call'
railties-7.2.2/lib/rails/railtie.rb:226:in `public_send'
railties-7.2.2/lib/rails/railtie.rb:226:in `method_missing'
rack-2.2.10/lib/rack/urlmap.rb:74:in `block in call'
rack-2.2.10/lib/rack/urlmap.rb:58:in `each'
rack-2.2.10/lib/rack/urlmap.rb:58:in `call'
unicorn-6.1.0/lib/unicorn/http_server.rb:634:in `process_client'
unicorn-6.1.0/lib/unicorn/http_server.rb:739:in `worker_loop'
unicorn-6.1.0/lib/unicorn/http_server.rb:547:in `spawn_missing_workers'
unicorn-6.1.0/lib/unicorn/http_server.rb:143:in `start'
unicorn-6.1.0/bin/unicorn:128:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/bin/unicorn:25:in `load'
/var/www/discourse/vendor/bundle/ruby/3.3.0/bin/unicorn:25:in `<main>'

OAuth2 설정은 다음과 같습니다::

A screenshot of a web interface showing a form for setting up OAuth2 client credentials, including fields for client ID, client secret, authorize URL, token URL, and other configuration options. (Captioned by AI)
A screenshot of a web interface showing a form for setting up OAuth2 client credentials, including fields for client ID, client secret, authorize URL, token URL, and other configuration options. (Captioned by AI)617×646 56.9 KB

The image displays a settings page for OAuth2 user details, including various fields for fetching, verifying, and retrieving information from OAuth2 user JSON URLs. (Captioned by AI)
The image displays a settings page for OAuth2 user details, including various fields for fetching, verifying, and retrieving information from OAuth2 user JSON URLs. (Captioned by AI)899×761 44.1 KB

2

안녕하세요, 오류를 삼중 백틱(```) 사이에 포맷해 주세요.

```
error message here
```
3

@Steve_John 게시글을 코드 블록 ```으로 로그가 포함되도록 포맷팅했습니다. 앞으로는 Nate가 위에서 제안한 대로 오류나 코드를 해당 방식으로 입력하는 것을 권장합니다.

이것이 faraday 포맷팅 문제이며 리프레시 시 인증이 성공적으로 이루어지고 있으므로, oauth2_debug_auth 설정을 끄시기를 제안합니다. 그렇게 하면 더 이상 오류를 볼 수 없을 것입니다.

4

네, Natalie. 말씀하신 대로 따르겠습니다. 업데이트해 주셔서 감사합니다.

5

현재 설정이 이렇습니다. 추측컨대, 이 설정을 비활성화하라고 요청하시는 것 같습니다. ::

OAuth2 인증 옵션, 이메일 확인, 아바타 경로, 디버깅 정보 설정 등이 포함된 Discourse 설정 페이지의 스크린샷. (AI 캡션)
OAuth2 인증 옵션, 이메일 확인, 아바타 경로, 디버깅 정보 설정 등이 포함된 Discourse 설정 페이지의 스크린샷. (AI 캡션)854×883 55.7 KB

6

이 옵션을 비활성화하고 다시 테스트해 보았는데, 재로그인 5회 시도 중 1회가 동일한 오류를 다시 일으켰습니다. 이 방법으로 문제가 완전히 해결되지 않았습니다.

The image displays an error message on a discussion forum, apologizing for an unexpected problem and suggesting that the software encountered an issue. (Captioned by AI)
The image displays an error message on a discussion forum, apologizing for an unexpected problem and suggesting that the software encountered an issue. (Captioned by AI)1462×255 12.3 KB

7

다시 살펴보니, oauth2_debug_auth 설정은 서버가 시작될 때 적용되는 것 같습니다. oauth 미들웨어와 디버깅용 로거가 그때 연결되므로 그렇습니다.

def register_middleware(omniauth)
  omniauth.provider :oauth2_basic,
  ...
      opts[:client_options][:connection_build] = lambda do |builder|
        if SiteSetting.oauth2_debug_auth && defined?(OAuth2FaradayFormatter)
          builder.response :logger,
                         Rails.logger,
                         { bodies: true, formatter: OAuth2FaradayFormatter }
        end
  ...
    }
end

대부분의 사이트 설정은 재시작이 필요하지 않지만, 이 특정 설정이 적용되려면 서버를 재시작해야 합니다.

그러나 근본적인 문제는 Faraday::TimeoutError (Timeout::Error)입니다. 로그를 끄라고 제안한 것이 문제를 해결해 주리라고 생각하지 않습니다. Discourse 인스턴스와 OAuth2 제공자 사이의 네트워크 문제를 확인해야 할 가능성이 높습니다.