Allow users to add login services to their accounts.
This package is part of the brettle:accounts-* suite of packages. See
brettle:accounts-deluxe
for an overview of the suite and a live demo.
-
When a logged in user attempts to login using credentials that don't belong to an existing user, this package adds those credentials to the logged in user, so they are available for future logins. Any other top-level or profile properties that would have belonged to a new user with those credentials are also non-destructively merged into the existing user.
-
When a logged in user tries to login using credentials that belong to an existing user, the user gets logged in as the existing user (unless that is otherwise prevented, for example by brettle:accounts-logout-to-switch).
-
Works with any login service (accounts-password, acccounts-google, etc.)
-
Works with
accounts-uiand other similar packages. -
Does not permanently monkey patch Meteor core.
meteor add brettle:accounts-add-serviceNothing to do. It should just work once installed.
When a service is added to an existing user, it is reported as a
Meteor.Error(Accounts.LoginCancelledError, 'New login not needed. Service will be added to logged in user.') because a new account was not created. The
accounts-ui package and the useraccounts suite will ignore that error when
adding an external login service, but not when adding the password service.
When adding the password service, they will display the "New login not
needed..." message as a red error message to the user. To suppress those error
messages, meteor add brettle:accounts-patch-ui.
This package adds a hasLoggedIn property to a user's account when he logs in,
and does a one-time migration to add the same property to existing users that
have the resume service created by the Meteor accounts system when a user logs
in. This is to ensure that a user counts as having logged in even if his
resume service is later removed (e.g. to force him to re-authenticate for
security reasons).
The migration runs from a Meteor.startup handler. It uses an internal
Mongo.Collection to keep track of whether it already started. This ensures
that it runs at most once and doesn't run on more than one server. If for some
reason you need to disable the migration, use:
AccountsAddService.databaseMigrationEnabled = false;