This video demonstrates adding a second middleware (auth) along with how to build out orders and stringing them together.
- View Offline
- [Instructor] Now let's figure out Authentication.…First, since it is Middleware,…we can build out the existing class…based on a Logging Middleware.…So we can go to our Middleware folder here.…Let's create a new one called Authentication.…And the best part is, since middleware has to be structured…exactly the same,…we can take our logging middleware,…copy,…paste it over to Authentication…and rename it.…We'll delete the actual logging portion.…Now, this is completely valid middleware.…
This doesn't do anything yet…but we've got the basis of what we're going to do.…Now, a lot of people's first impulse…will be to build the authentication check right here.…Build it directly into the middleware.…While it would technically work,…that's not where it belongs.…If you think about it, authentication is a user function.…Therefore, it should probably be on a user class.…So let's go over to our Models folder.…And we'll create a new file called, User.…Just User.php.…And once again, if we look at our Message Class,…we'll realize this is very reusable.…
This course begins with a simple application specification and builds it one step at a time. Each chapter includes a key concept, with examples from other public APIs, and then shows how to build it yourself with Slim. Learn about URL routing, validating input, and generating response codes and hypermedia payloads. Like any project, the first implementation may be a little messy but don't worry. The last chapter covers refactoring and what it takes to scale and support the API going forward.
- Understanding the project goals
- Setting up the database
- Adding authentication in Slim
- Using cross-framework and authentication middleware
- Creating a read-write API in Slim
- Uploading files via the API
- Adding file security
- Creating payloads and response codes in Slim
- Scaling your API