Always set Auth interface in DI to the correct plugin's Auth implementation #13279
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Auth interface is used for more than authentication, such as getting the configured Login plugin's name, and it is possible for code to try and re-authenticate using the stored auth. In which case, we would always want this interface set to the real implementation.
This PR does that if the SessionAuth succeeds and sets the token auth to the authenticated user's token auth, so reauthentication w/ plugin auths should work (since all Auth implementations are required to support authenticating by token auth alone).
CC @matomo-org/core-team