Compatibility

Compatible with Meteor 2.4

This repository provides versions for the package useraccounts:iron-routing that are compatible with latest Meteor. This is necessary because the author is not maintaining package anymore.

Changes

v1.15.0
- Updates iron:router to 1.2.0, compatible with jQuery 3.0.0
- Updates useraccounts:core to 1.15.0

Iron Router add-on for User Accounts

User Accounts is a suite of packages for the Meteor.js platform. It provides highly customizable user accounts UI templates for many different front-end frameworks. At the moment it includes forms for sign in, sign up, forgot password, reset password, change password, enroll account.

This package is an optional add-on for integration with Iron Router.

Configuration

Before you configure routes for User Accounts with Iron Router, you will need to make sure you have set a few default configuration items.

Assuming you have a main layout that looks like this:

<template name="myLayout">
  {{> yield region='nav'}}

  <div id="content">
    {{> yield}}
  </div>

  {{> yield region='footer'}}
</template>

You would configure the router and this package to use it like this:

1Router.configure({
2    layoutTemplate: 'masterLayout',
3    yieldTemplates: {
4        myNav: {to: 'nav'},
5        myFooter: {to: 'footer'},
6    }
7});
8
9AccountsTemplates.configure({
10    defaultLayout: 'myLayout',
11});

NOTE: The above configs must load BEFORE your AccountsTemplates routes are defined (next section).

Routes

There are no routes provided by default. But you can easily configure routes for sign in, sign up, forgot password, reset password, change password, enroll account using AccountsTemplates.configureRoute. This is done internally relying on the awesome Iron-Router package.

The simplest way is to make the call passing just the route code (available codes are: changePwd, enrollAccount, forgotPwd, resetPwd, signIn, signUp):

1AccountsTemplates.configureRoute('signIn');

This will set up the sign in route with a full-page form letting users access your app.

NOTE: some routes need other useraccounts' regular options to be set in advance. Please make sure to have your calls to AccountsTemplates.configureRoute be executed after your calls to the regular AccountsTemplates.configure

Actually, you can also pass in more options to adapt it to your needs with:

1AccountsTemplates.configureRoute(route_code, options);

The following is a complete example of a route configuration:

1AccountsTemplates.configureRoute('signIn', {
2    name: 'signin',
3    path: '/login',
4    template: 'myLogin',
5    layoutTemplate: 'myLayout',
6    redirect: '/user-profile',
7});

Fields name, path, template, and layoutTemplate are passed down directly to Router.map (see the official iron router documentation here for more details), while redirect permits to specify where to redirect the user after successful form submit. Actually, redirect can be a function so that, for example, the following:

1AccountsTemplates.configureRoute('signIn', {
2    redirect: function(){
3        var user = Meteor.user();
4        if (user)
5          Router.go('/user/' + user._id);
6    }
7});

will redirect to, e.g., '/user/ae8WQQk6DrtDzA2AZ' after succesful login :-)

All the above fields are optional and fall back to default values in case you don't provide them. Default values are as follows:

Action	route_code	Route Name	Route Path	Template	Redirect after Timeout
change password	changePwd	atChangePwd	/change-password	fullPageAtForm
enroll account	enrollAccount	atEnrollAccount	/enroll-account	fullPageAtForm	X
forgot password	forgotPwd	atForgotPwd	/forgot-password	fullPageAtForm	X
reset password	resetPwd	atResetPwd	/reset-password	fullPageAtForm	X
sign in	signIn	atSignIn	/sign-in	fullPageAtForm
sign up	signUp	atSignUp	/sign-up	fullPageAtForm
verify email	verifyEmail	atVerifyEmail	/verify-email	fullPageAtForm	X
resend verification email	resendVerificationEmail	atresendVerificationEmail	/send-again	fullPageAtForm

If layoutTemplate is not specified, it falls back to what is currently set up with Iron-Router. If redirect is not specified, it default to the previous route (obviously routes set up with AccountsTemplates.configureRoute are excluded to provide a better user experience). What more, when the login form is shown to protect private content (see Content Protection, the user is redirect to the protected page after successful sign in or sign up, regardless of whether a redirect parameter was passed for signIn or signUp route configuration or not.

Besides the above list of routes you can also configure ensureSignedIn in order to specify different template and layout to be used for the Iron Router ensuredSignedIn plugin (see Content Protection):

1AccountsTemplates.configureRoute('ensureSignedIn', {
2    template: 'myLogin',
3    layoutTemplate: 'myLayout',
4});

in this case, any field different from template and layoutTemplate will be ignored!

Content Protection

useraccounts:iron-routing package come with an Iron Router plugin called ensureSignedIn which permits to prompt for the sign in form for the pages requiring the user to be signed in. It behaves nicely letting the required route path inside the address bar and bringing you back to the same route once logged in.

Please note that a fake version of ensureSignedIn is also available on server-side to allow for shared routing files, but there's no way to check whether a user is logged in or not on a server-side route!

To protect all you routes use it like this:

1// Protect all Routes
2Router.plugin('ensureSignedIn');
3
4// If you are using other plugins, pay attention to their load order.
5// Use *after* so you don't get 404's on your protected routes.
6Router.onBeforeAction('dataNotFound');

While in case you want to protect almost all your routes you might want to set up the plugin this way:

1Router.plugin('ensureSignedIn', {
2    except: ['home', 'atSignIn', 'atSignUp', 'atForgotPassword']
3});

while an even better example could be

1Router.plugin('ensureSignedIn', {
2  except: _.pluck(AccountsTemplates.routes, 'name').concat(['home', 'contacts'])
3});

if, instead, it's only a bunch of routes to be protected you could do (even more than once inside different files...):

1Router.plugin('ensureSignedIn', {
2    only: ['profile', 'privateStuff']
3});

Moreover, if you wish to customize the template and layout to be used you can change them with:

1AccountsTemplates.configureRoute('ensureSignedIn', {
2    template: 'myLogin',
3    layoutTemplate: 'myLayout',
4});