RoutingError produced by OAuth2 module in version 5.2.3

Technical assistance
1

Infos:

  • Used Zammad version: 5.2.3-1667896726.e5427da9.bullseye
  • Used Zammad installation type: package
  • Operating system: Debian 11
  • Browser + version: all

Expected behavior:

  • Generic OAuth2 should be disabled and the ActionController should not try to route to that authentication mechanism

Actual behavior:

  • messages like the following show up in the production.log

    #---/var/log/production.log---
[..]
E, [2022-11-09T16:08:33.541794 #1136185-24398640] ERROR -- : No route matches [GET] /auth/oauth2 (ActionController::RoutingError)
[..]

Steps to reproduce the behavior:

We have been using Zammad since version 3.x and used the generic OAuth integration for authenticating zammad accounts that were already in our customer database.
We upgraded Zammad to version 5.x and switched authentication of users in our customerdatabase to the LDAP integration.
We probably forgot to disable the OAuth mechanism prior to the upgrade and now of course it is no longer available:


My guess is that there is a configuration for the OAuth mechanism left over in the database.
Is there a way to disable the mechanism e.g. via the rails console?

2

It turns out that a long forgotten monitoring tool was scraping the endpoint /auth/oauth2

3

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.