Skip to content

Prevent disabled user from logging in on reactive applicationsΒ #7113

Closed

Description

@eleftherias

Summary

In servlet applications, if a user account is disabled, locked or expired, then the user is not permitted to log in.
In reactive applications, the user is still permitted to log in regardless of their account status.

The reactive applications should behave like the servlet application by default, and prevent disabled, locked or expired accounts from logging in.

Activity

  1. eleftherias commented on Jul 17, 2019

    @eleftherias
    ContributorAuthor

    This functionality is handled by the pre and post authentication checks in the AbstractUserDetailsAuthenticationProvider for servlet applications.
    Reactive applications do not have pre authentication checks and have a noop post authentication check, as seen in UserDetailsRepositoryReactiveAuthenticationManager.
    Instead, they should have the same checks that the servlet applications have.
    Additionally, there should be a higher level class, similar to AbstractUserDetailsAuthenticationProvider for reactive applications, where these checks are defined.

  2. added a commit that references this issue on Jul 29, 2019
    8e6e975
  3. added this to the 5.2.0.M4 milestone on Jul 29, 2019
  4. self-assigned this
    on Jul 29, 2019
  5. added a commit that references this issue on Aug 26, 2019
    86b0dea
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

in: webAn issue in web modules (web, webmvc)type: enhancementA general enhancement

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions