RESTful Web API in .NET Core - The Advanced Guide (.NET 10)

Explore dynamic filtering in a .NET Core gateway using a filter by and filter query with a switch on properties like name, details, and rate, plus min and max rates.

Add sort by and sort order to a .NET Core API, enabling sorting of villas query. Sort by name, rate, occupancy, square feet, or id in ascending or descending order.

Apply pagination by using page and page size defaults: page 1, page size 10, max 100. Determine skip as (page - 1) times page size and take page size records.

Learn to expose pagination details in response headers of a .NET core web API, including current page, page size, total count, and total pages.

Utilize dotnet identity to register application users via user manager, validate emails, create or assign roles with role manager, and rely on identity helpers for sign in and sign out.

Learn to implement login with identity in a .NET core API, validating hashed passwords with UserManager, retrieving roles, and returning a token-based login response.

Implement an image service interface for the .NET core RESTful API, including upload (returns path), delete (returns success), and validate (checks image type) with 5 MB limit and PNG/JPEG.

Configure the image service in program.cs by registering its interface and implementation, enable static files for the wwwroot folder, and register the file service for API access.

Learn to accept images in FromForm for villa creation in a .NET Core RESTful API, injecting an image service and updating the VillaCreateDto to handle form-file uploads.

Consume the image file service in the villa controller to upload images, validate formats and size, store the image url, and delete old images during update and delete operations.

Create a generic extension method that converts any object to form data, handling file properties as streams so the API can create villas with images.

Consume the extension in villa service by passing multipart form data directly to the message content, update base service to pass multipart data when present, and use json content otherwise.

Create the villa creation view to consume the API via multipart/form-data, adding an image file upload with a live preview and JPEG/PNG format support.

Implement an image uploader with a live preview. Use a JavaScript onchange function to read the file as a data URL with FileReader and display it in the preview container.

Learn how to display villa images by resolving relative paths with a get image url helper that appends the api base url and uses a placeholder when missing.

This lecture demonstrates deleting a villa and automatically removing its associated image, ensuring data integrity by syncing villa deletion with image removal.

Highlight refactoring the auth controller to apply single responsibility by moving token management and claims retrieval to a token provider with set, get, clear token, and get claims from token.

Build a token provider service for a .NET Core API that uses http context accessor to set, get, and clear session tokens and to create a principal from JWT claims.

Consume the token provider service in the auth controller and sign in. Retrieve the principal from the token, set the access token, and redirect.

Fix the villa get endpoint by removing the admin role restriction to allow anonymous access and update the home page image using the sd.get image url.

Create a refresh token table by modeling unique id, user id, token value, valid flag, and expiration time, linked to the access token, then add a dbset and migrate database.

Add a refresh token to the token DTO, rename the class to token DTO, and generate an access token with a refresh token that has expiration and expires at.

Move the JWT token generation to a dedicated token service, inject configuration, user manager, and application DB context, and register the service to centralize token management.

Implement refresh token endpoints for token service, generate access and refresh tokens, save the refresh token with user id and JWT token id, and revoke by marking is valid false.

Generate a cryptographically secure 64-byte refresh token by filling a byte array with random values, encoding to base64, and checking for uniqueness in the database, regenerating recursively if duplicates.

Generate and persist a new refresh token in the token service during login, alongside the JWT, with a two-minute access token and a five-minute refresh expiry.

Add a new claim in the access token to store the token ID, bridging the access and refresh tokens so both carry the same JWT token ID.

Demonstrates refreshing a two-minute access token with a five-minute refresh token to access a protected villas endpoint, and outlines invalidating old tokens if compromised.

Invalidate the complete token family by setting all tokens' is valid to false and saving changes, forcing re-login when a compromised refresh token is used.

Extend a restful web API in .NET Core by adding a refresh token flow, updating the token provider to manage access and refresh tokens, and exposing endpoints for both tokens.

Automatically refresh expired access tokens via the refresh token endpoint, update the session with new tokens, and prevent duplicate refresh calls for a stable login.

Implement a token refresh flow in the base api call by awaiting the refresh token, retrying the request after a successful refresh, and redirecting to login if refresh fails.

The lecture demonstrates implementing a refresh token flow in a .NET restful web api, renewing access tokens automatically after a session expiry and avoiding re-login.

Demonstrates implementing a refresh token flow by validating five-minute expiry and redirecting to login when expired, then signs out from the cookie authentication scheme and redirects to login.

Extend part one by adding file uploads and image storage in a dotnet rest api, consuming the endpoint from web project, and exploring jwt authentication, refresh tokens, and azure deployment.

Part two requires completing part one, where we built a RESTful API with dotnet core. It enhances the prior application and assumes the part one basics from ground zero.

Prepare for part two of the rest api course by downloading the startup project from Dotnet Mastery, opening the Magic Villa API, and reviewing resources, with no changes yet.

Configure the .NET7 RESTful Web API by updating the appsettings.json connection string to a local SQL Server, create the Magic Villa API part two database, and run migrations.