-
-
Notifications
You must be signed in to change notification settings - Fork 402
Google OAuth2 plugin #2232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Linking #2212 where another I'm adding this to the agenda for tonight's issue chat. |
It was decided, that this will be covered in a plugin. Now waiting for said plugin. |
@dune73 Can you, please, create a new repository for this plugin? Probably with name |
Of course. |
Let me know if you want to change the description (top right) and GH does not grant you permissions. |
Ready for review! |
Plugin is ready: https://github.com/coreruleset/google-oauth2-plugin. Closing! |
Uh oh!
There was an error while loading. Please reload this page.
Motivation
Lots of users are reporting problems with Google OAuth2 callback requests as it's
scope
argument usually contains string.profile
, which is triggering rule930120
. We already proposed a solution for this (see PRs #1958 and #2222) but i don't think that our core ruleset should contain bypasses for specific software and services.Proposed solution
I suggest reworking this into an official plugin, which will contain 3 rules:
930050
930051
from Fixing Google OAuth2 detection #2222Prototype of this plugin is ready.
The text was updated successfully, but these errors were encountered: