On Meteor 1.11, adding the defaultFieldsSelector config of Accounts.config has two problems:

1. BUG: it makes the Accounts.forgotPassword always return an error of "No such email" if the defaultFieldsSelector doesn't have email as a default field. It seems to be missing an internal fields selector on the internal query to the users collection.
2. LIMITATION: the Accounts.onLogin callback has no way of configuring the fields returned in the user that's given in the callback parameter.

Expected behavior:

forgotPassword should work without errors when the Accounts.config.defaultFieldsSelector doesn't have the email as a default field. It seems to be missing a selector in it's internal query to the users collection.
Accounts.onLogin should allow to configure a selector for the user object that's given inside the callback parameter.

To reproduce the problem:

1. add Accounts.config({defaultFieldsSelector: {_id: 1}}); somewhere on the project (both client and server).
2. to see the forgot password error call:

Accounts.forgotPassword({ email: value }, (error) => {
	if (error) {
		console.log(error);
	} else {
		console.log("success");
	}
});

3. Call Accounts.onLogin((loginData) => {console.log(loginData.user)}); to see that the user always return only the _id, but there's no way to make it return the username or email for only that callback unless adding those values to the defaultFieldsSelector.