Closed warcooft closed 2 months ago
The changes in the OAuthController
class enhance the user authentication process by introducing a new private property to track user existence. The callBack
method now checks if a user is banned and redirects accordingly. Additionally, the logic for creating new users has been refined to prevent self-registration if the user already exists, ensuring a more streamlined control flow during the login attempt.
File | Change Summary |
---|---|
src/Controllers/OAuthController.php |
Added a private nullable User property $userExist and modified the callBack method to handle user existence and banned status checks. |
callBack
method in the OAuthController
class to enhance error messages related to account not found scenarios, which is directly relevant to the changes made in the main PR that also involves modifications to the callBack
method in the same class.callBack
method in the OAuthController
class to handle access denial scenarios, which is related to the overall error handling improvements made in the main PR.enhancement
In the meadow where bunnies play,
A change was made to brighten the day.
With checks for users, both lost and found,
A safer login now hops around! 🐰✨
Banned or free, all will see,
A joyful dance in harmony!
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
I'm curious, why banned users still can log in.
Hi @warcooft,
The user banning feature was added in Shield v1.0.0-beta.4. However, I believe that Shield OAuth was released before version v1.0.0-beta.4.
I'm curious, why banned users still can log in.
Summary by CodeRabbit
New Features
Bug Fixes