You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, it was not necessary to use Symfony's security system. We only needed a persistent anonymous user, which could be well mapped by AssignUserIdOnKernelRequest. This looks different with #6 and #130. With #6 registered users should be able to log in via whatever. With #130 the /metrics endpoint for php shall be secured with basic auth. Instead of adapting the listener AssignUserIdOnKernelRequest to this or building a more complex self-written solution, the security system of Symfony shall be used. This can handle all needs.
Upon arrival, ArrivialAuthenticator creates a new user in the
identity context and authenticates them in the session #153.
The current implementation covers what AssignUserIdOnKernelRequest
did before. It adds some complexity, but opens the way for #130 to
secure the /metrics endpoint for php with basic auth, and #6 to eventually
authenticate the user in any way.
Previously, it was not necessary to use Symfony's security system. We only needed a persistent anonymous user, which could be well mapped by
AssignUserIdOnKernelRequest
. This looks different with #6 and #130. With #6 registered users should be able to log in via whatever. With #130 the/metrics
endpoint for php shall be secured with basic auth. Instead of adapting the listenerAssignUserIdOnKernelRequest
to this or building a more complex self-written solution, the security system of Symfony shall be used. This can handle all needs.This blocks issues #6 and #130.
The text was updated successfully, but these errors were encountered: