[NOISE] Hey all, I'm Kenneth, the Django teacher here at Treehouse.

If you've been following along with me, you've built a lot of stuff with Django.

But one thing you haven't really seen is how to do aut with Django, and

of course by aut, I mean both authentication and authorization.

Hm, those two words sound really similar.

Aren't they the same thing?

Actually no,

authentication is all about connecting some credentials to an incoming request.

In other words making sure a user is who they say they are.

By default Django does this with a username and password.

Once a user authenticates themselves that authentication is stored in their session

and that session authenticates the request.

Authorization on the other hand is about ensuring that the user has permission

to do the action they want to do.

For example, you might not want just any user to be able to delete job listings,

or cat photos.

Those actions are only for certain users who are authorized to do them.

Before you can determine if a user can do something,

you have to identify who they are.

Well, except for things you won't let just anyone do.

So, the first thing to look at is authentication.

I've built most of a project for

this course and it's missing a bunch of auth related features.

I figured we could build them together.

For now though, let's hop over to Work Spaces so I can give you a little tour.

So, I wanted to show you around this project before we start working on it

too much.

So I've named it MSG for message,

not for monosodium glutamate.

And so there it is, it's a social network, so you would join.

You would have communities that you could belong to.

You'd post messages to the communities or to the general public.

And just share your information and thoughts and everything.

This theme isn't from me,

it's not even from Treehouse actually it's from a site called creative Tim.

It was a free theme that I kind of mess around with a little bit.

So yeah it's pretty cool.

This is the home page and then if you go to the Posts page this is where you

see posts and you can see I basically ripped off Twitter.

There's a user icon, there's whatever display name you want.

There's a user name, there's when the thing was posted, where it was posted,

if it was posted anywhere and then what the actual post was.

You can go see the post, that a user has posted, you can go see

a specific post which you can see, these are marked down, which is kind of cool.

I realized now I should have had this on that page.

But hey, there's a thing for all of you to add in and

then you can also, sorry I may go back to here.

You can also go look at the posts that are in a given community.

Here we go. And you can join the community or

you can leave the community if you are logged in.

So, speaking of, I wanna talk about there's

this README here that has are the usual default information.

There is a todo here that has stuff that needs to be done.

Some of this we're gonna get to, some of this we may not.

And then there's the credits down here that I talked about with creative Tim and

icons8 for some of the icons.

All right, so let's try running these tests here.

I just wanna do python manage.py test.

And it's gonna run the test and if I remember correctly they should all pass.

Right, but we have an expected failure, so

I need to fix that, I don't want to be there to be an expected failure.

So that's something we'll get to in the next video.

I don't have tests written for the entire app, and everything that's missing.

But between tests and that README, I think everything is covered.

Now that you have an idea of what the site is, and what it's missing,

I think it's time to make some of those views require a user to be logged in.

That's coming in the next video.