Heads up! To view this whole video, sign in with your Courses account or enroll in your free 7-day trial. Sign In Enroll

PHP User Authentication

Preview

Start a free Courses trial
to watch this video

Sign up for Treehouse

Working with Cookies

4:24 with Alena Holligan

Now that we have the JWT ready, we will use the HTTP Foundations package to set and retrieve cookies.

NOTE: Because we set our extra parameter to accept an array, make sure you pass the cookie as an array.

Tips for Reading and Writing Cookies

To test reading a cookie after login: on index.php

if (request()->cookies->has('access_token')) {
    echo "logged in";
} else {
    echo "not logged in";
}

If the cookie isn't working properly, one of the most common reasons is that the COOKIE_DOMAIN in the .env file is not set properly.

When using workspaces it should be YOUR workspace url, which would look something like 

COOKIE_DOMAIN=port-80-m1m8flu0vu.treehouse-app.com

When working locally, it should be

COOKIE_DOMAIN=localhost

Related Discussions

Have questions about this video? Start a discussion with the community and Treehouse staff.

Sign up

    Related Discussions

    Have questions about this video? Start a discussion with the community and Treehouse staff.

    Sign up

    Cookies can be a bit tricky to work with when using 0:00
    only the built in PHP functions. 0:02
    Part of the reason we're using the symphony package for 0:05
    getting the request is the ease of setting the cookie on the request object. 0:07
    To create our cookie, 0:13
    we used a cookie class from the symphony package we pulled in. 0:14
    There are a few parts to the cookie. 0:35
    First the name of the cookie. 0:37
    For which we'll use access token. 0:39
    Next, the jwt. 0:44
    Followed by the expiration time. 0:50
    The path and the domain. 0:56
    The last part is important as this is what tells the cookie where it lives. 1:09
    Without it, it will live in this session and 1:14
    may not always be available when you're looking for it. 1:17
    Once we have our access token, we want to redirect the user back with a cookie. 1:20
    We're going to modify our redirect function a little bit to allow for 1:26
    a cookie to be passed in. 1:29
    Open the functions file. 1:31
    Find the redirect function. 1:34
    We're going to add a new property that defaults to an empty array. 1:41
    This is so that we can expand in the future without too much work. 1:48
    After we set a variable for the response, and 1:53
    before we send it, we need to check for cookies inside of the extras array. 1:56
    If key exists. 2:00
    Cookies in extra. 2:05
    If it does, then we'll loop over each of the cookies so that we can set multiple 2:14
    cookies on the response headers using the SET cookie function. 2:18
    Foreach extra 2:22
    cookies as cookie. 2:26
    Response-> headers-> 2:36
    setCookie and pass the cookie. 2:41
    Now let's add the redirect with a cookie. 2:49
    Redirect to the home page and pass in the cookie. 2:58
    Let's modify our home page to read the cookie just so 3:15
    that we know that we're logged in. 3:18
    We need to require our bootstrap file first. 3:25
    And then if 3:37
    (request()->cookies->has('access_token'). 3:39
    Then we're just going to echo logged in. 3:53
    Let's take a look at what we have built so far, and log in to our system. 3:59
    Great, now that you know how to redirect a user with cookies set, give it a try and 4:13
    see if you can set the registration to automatically 4:18
    log a user in when they sign up. 4:21

    You need to sign up for Treehouse in order to download course files.

    Sign up

      You need to sign up for Treehouse in order to set up Workspace

      Sign up