Authentication in Ember
This training will involve a lot of following code and and exploring the Chrome Inspector and utilizing Ember Inspector. It is recommended that you comment code or take notes.
By the end of this, developers should be able to:
- Implement token authentication in an Ember application.
- Enforce authentication in protected routes.
- Fork and clone this repository.
- Install dependencies with
- Start any API based on a recent version of the Rails API Template or the Express API Template.
- Start the front-end server with
From end to end
Watch as I sign up for a new account on our demo app.
Other than the flash messages on the page, did anything change? What about in the Chrome Developer Tools?
Take some time and sign in on your own, and check to see if anything in the Chrome Dev Tools has changed.
Now that we have added a key tool to our personal developer toolkit lets look at how it's implemented.
Let's walk through file by file to see what's happening. I will ask developers to guide me through the files while correcting any misunderstandings.
First let's start down the template and component trail, then we'll work our way up with actions.
Remember: Data down, actions up.
While going up the Ember hierarchy we may need to stop a some point to discuss services.
- Implementing Authentication with Ember Services - Ember Igniter
- jpadilla/ember-simple-auth-token: Ember Simple Auth extension that is compatible with token-based authentication like JWT.
- simplabs/ember-simple-auth: A library for implementing authentication/authorization in Ember.js applications.
- Create your first Ember 2.0 app: From authentication to calling an API
- All content is licensed under a CCBYNCSA 4.0 license.
- All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact firstname.lastname@example.org.