Chapters

14 Chapters | 54:16 |

01

Start Securing the App!

4:20
02

JSON Web Tokens (are awesome)

4:35
03

LexikJWTAuthenticationBundle

4:54
04

The "Fetch a Token" Endpoint Test

4:09
05

Create a Shiny JSON Web Token

4:53
06

Authenticate a Request with JWT

2:18
07

JWT Guard Authenticator (Part 1)

5:39
08

Registering the Authenticator (Part 2)

2:12
09

Lock down: Require Authentication Everywhere

3:09
10

The "Entry Point" & Multiple Firewalls

4:16
11

JSON Errors in your API

4:15
12

ResponseFactory: Centralize Error Responses

3:36
13

Graceful Errors for an Invalid JWT

3:20
14

JWT: Other Things to Think about

2:40

This tutorial has a new version, check it out!

> APIs > Symfony RESTful API: Authentication with JWT (Course 4)

Buy Access to Course

10.

The "Entry Point" & Multiple Firewalls

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $10.00

Previous Chapter

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

3 Comments

Sort By

Login or Register to join the conversation

Shaun T. 8 years ago

Thank you for writing this tutorial, I’m really enjoying folllowing it.

I started building my web app in a traditional way. After building some Ajax into my app I am thinking it would be cool to make the whole front end talk to the back end via JSON api end points.

Is there any reason why a traditional login form on a web app couldn’t use an api end point for authentication? That way there would be no need for multiple firewalls...

|

Victor SFCASTS Shaun T. 8 years ago

Hey Shaun,

Thanks for the kind words!

Sounds cool! Starting simple is a good way to quickly release the first version of your project so users can actually use it while you're coding more advanced version of the same project - this is a perfect strategy ;)

Hm, I don't see any issue, probably it just bring some complexity into your code, I mean, it consume more time to be implemented.

Cheers!

|

Shaun T. Victor 8 years ago

Many thanks Victor, I appreciate you clarifying that for me :)

|

This tutorial uses an older version of Symfony. The concepts of API tokens & JWT are still valid, but integration in newer Symfony versions may be different.

Symfony 3

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=5.5.9",
        "symfony/symfony": "3.0.*", // v3.0.3
        "doctrine/orm": "^2.5", // v2.5.4
        "doctrine/doctrine-bundle": "^1.6", // 1.6.2
        "doctrine/doctrine-cache-bundle": "^1.2", // 1.3.0
        "symfony/swiftmailer-bundle": "^2.3", // v2.3.11
        "symfony/monolog-bundle": "^2.8", // v2.10.0
        "sensio/distribution-bundle": "^5.0", // v5.0.4
        "sensio/framework-extra-bundle": "^3.0.2", // v3.0.14
        "incenteev/composer-parameter-handler": "~2.0", // v2.1.2
        "jms/serializer-bundle": "^1.1.0", // 1.1.0
        "white-october/pagerfanta-bundle": "^1.0", // v1.0.5
        "lexik/jwt-authentication-bundle": "^1.4" // v1.4.3
    },
    "require-dev": {
        "sensio/generator-bundle": "^3.0", // v3.0.6
        "symfony/phpunit-bridge": "^3.0", // v3.0.3
        "behat/behat": "~3.1@dev", // dev-master
        "behat/mink-extension": "~2.2.0", // v2.2
        "behat/mink-goutte-driver": "~1.2.0", // v1.2.1
        "behat/mink-selenium2-driver": "~1.3.0", // v1.3.1
        "phpunit/phpunit": "~4.6.0", // 4.6.10
        "doctrine/doctrine-fixtures-bundle": "^2.3" // 2.3.0
    }
}

Previous Chapter

Next Chapter