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