.NET 5 & .NET Core 3.1 Web API & Entity Framework Jump start.
- Model-View-Controller (MVC) pattern
- Asynchronous implementations
- Data-Transfer-Objects (DTOs)
- CRUD (Create, Read, Update, Delete)
- HTTP request methods (GET, POST, PUT, DELETE)
- Persistence
- Object-Relational-Mapping
- SQL Server database
- Code-First Migration
- CRUD with Entity Framework Core
- User registration and login
- Cryptography algorithm HMACSHA512
- JSON Web Tokens
- One-To-One
- One-To-Many
- Many-To-Many
- Swashbuckle Filters
- AutoMapper
- Entity Framework Core Design
- Entity Framework Core SqlServer
- JWT Bearer
dotnet ef migrations add InitialCreate
dotnet ef database update
On the JWT page "Debugger" one can take a deeper look into the token generated by /Auth/Login
- To a valid signature verification, replace
your-256-bit-secret
on the UI for the"AppSettings:Token"
value on theappsettings.json
file.
cd dotnet-rpg
dotnet run
Follow path: https://localhost:5001/swagger/index.html
-
To test secured methods with Swagger
- run
/Auth/Login
with a registered user - copy the token generated
- on right top of the page click on
Authorize
and paste the value from previous step, like the example given on the screenbearer <TOKEN>
- after successfully loging, the locked methods (closed lock on right corner) can be tested and the message shown should be like the image below
- run