This pull request adds the options entityUsernameField and entityPasswordField, corresponding to the fields on the user entity that contain the username and password fields respectively. If these options are not defined the username and password fields default back to usernameField and passwordField, maintaining backwards compatibility. This allows the separation of the {username,password}Fields on the user entity and on the incoming authentication request.
Summary
This pull request adds the options
entityUsernameField
andentityPasswordField
, corresponding to the fields on the user entity that contain the username and password fields respectively. If these options are not defined the username and password fields default back tousernameField
andpasswordField
, maintaining backwards compatibility. This allows the separation of the {username,password}Fields on the user entity and on the incoming authentication request.Concretely, this allows the following use case:
authentication-local options:
authentication request:
user entity:
Open questions
requestUsernameField
instead ofentityUsernameField
? Or all three?