Google OAUTH2 results in 404

[MrGeneration]

@gabe2385

@MrGeneration I am wondering if you did a clean install instead of getting it from an update?

Actually I did both
But what might be different is that my update steps are always from version to version (so not jumping from 2.9 to 3.1).

Two things:

First of all I want to apologize, I was partly on a really thin icey road here.

• 10 days ago, just before we released 3.1, we adressed an CSRF-Issue that was blocking our release
  • this changed some of our mechanics (see: Maintenance: Applied required changes to resolve 'omniauth' CVE-2015-… · zammad/zammad@9503ff2 · GitHub )
  • this means: If you don’t have this line in your file ( zammad/app/assets/javascripts/app/views/login.jst.eco at 9503ff20cefcfc39cb451562d7ec4fd440198564 · zammad/zammad · GitHub ), something wasn’t correct. You have to find this line within the form for each login provider
    • if you find this in your file, but not in the source code of the webapp being delivered, recompile the app with: zammad run rake assets:precompile
      • this step does not apply to docker containers, as they should do this on every start
• If you still have issues, just to be sure, you can do the following things
  • ensure this is not a caching issue (by proxy, browser)
  • run /op/zammad/contrib/packager.io/postinstall.sh to ensure all migrations have run

Hopefully this will help you.
Please note: The above only applies for the login buttons within the login page.

There’s a bug hitting the profile section (e.g. when you try to link any third party account (I totally ignored that in my pasts posts, sorry!)), that currently makes it impossible to link third party accounts:

Linking of external account in profile is broken

We’re working on fixing this bug at the minute I’m writing.