Accounts-ui loginButtons: configuring a redirect target after successful sign-in

Answer

There is no built-in accounts-ui option to set a redirect after sign-in. The documented integration point is the client-side Accounts.onLogin callback, combined with your router's programmatic navigation.

Confirmed facts

• Accounts.ui.config() only controls UI-specific fields such as passwordSignupFields and OAuth request permissions; it does not expose a post-login navigation setting.
• Accounts.onLogin is invoked for every successful login flow: password (Meteor.loginWithPassword), resume-token (Meteor.loginWithToken), and OAuth services.
• The callback receives an object containing the authenticated user; on failure the callback is not run at all, so failed logins leave the user on the current page.

Recommended steps

1. Add the following client-side code (for example in client/main.js):

   Accounts.onLogin(() => {
     // Defer navigation until the current flush and any
     // login method callbacks have finished
     Meteor.setTimeout(() => {
       FlowRouter.go('/dashboard');
     }, 0);
   });

2. If you use a different router (kadira:flow-router, ostrio:flow-router-extra, or another), replace FlowRouter.go with that router's programmatic navigation method.
3. Alternatively, use Tracker.afterFlush instead of Meteor.setTimeout to guarantee Blaze has finished rendering before navigating:

   Accounts.onLogin(() => {
     Tracker.afterFlush(() => {
       FlowRouter.go('/dashboard');
     });
   });

Verification

1. Sign in with accounts-password; confirm the URL changes to /dashboard and the login dropdown closes cleanly.
2. Test with a valid resume token (Meteor.loginWithToken(token)) and verify the same redirect occurs.
3. Test with an OAuth service (for example Google) and confirm the redirect fires there too.
4. Attempt a login with incorrect credentials; ensure the URL does not change and an error is displayed, confirming the callback only runs on success.

Pitfalls to avoid

• Navigating synchronously inside the callback can fire while the accounts-ui dropdown is still closing, causing a visible flash; the deferred call avoids this.
• Using window.location.href bypasses Blaze reactivity and the router's data dependencies; always prefer the router's programmatic navigation.
• Because Accounts.onLogin does not run on failure, handle errors via the login method's own callback or Accounts.onLoginFailure if you need to surface a message.