This makes it possible for existing deployments to have this working with SSO. Otherwise, the user would end up authenticated with the "default" auth source when accessing the web interface, and "another" auth source when logging in via SAML.