No alternative entry point type can be configured
Theoretically it is possible to use another type of entry point than the pre-configured WebRedirect. In practice, however, it is not possible to override the pre-defined type due to a bug in the corresponding parsing function in AuthenticationProviderManager.
While being on it, the setting names and structure could need some improvement to assert that only one entry point can be defined at all. The result should look like this:
[!!!][BUGFIX] Alternative entry points can be configured again
This fix allows for using other than the pre-defined WebRedirect
entry points (for example the HTTP Basic entry point).
In order to avoid confusion, this patch also streamlines the setting
names for authentication providers. It makes sure that only one entry
point can be defined at all and adjusts the naming of other settings
to be in line with other FLOW3 setting conventions.
The keys of settings for the authentication provider have changed as
provider: '(a class name)'
providerOptions: [ ... options ... ]
token: '(a class name)'
entryPoint: '(a class name)'
entryPointOptions: [ ... options ... ]