Now that our data model can properly store the refresh tokens, we can move our focus to the Web API, starting with the ViewModels that will carry the refresh token from the server to the client and vice versa.
- Preface
- Getting Ready
- Two players, one goal
- A full-stack approach
- Single-Page Application
- A sample Single-Page Application project
- Preparing the workspace
- Looking around
- Getting to work
- References
- Suggested topics
- Summary
- Backend with .NET Core
- Frontend with Angular
- Navigation pattern
- Master/detail binding
- Adding additional lists
- Two-way data binding
- Client-side routing
- Full-Scale test
- Suggested topics
- Summary
- Data Model with Entity Framework Core
- Client-Server Interactions
- Style Sheets and UI Layout
- Forms and Data Validation
- Authentication and Authorization
- To auth, or not to auth
- Proprietary auth with .NET Core
- Updating the database
- Authentication methods
- Implementing JWT authentication
- Enforcing authorization
- Suggested topics
- Summary
- Advanced Topics
- Token expiration and refresh tokens
- New user registration
- Third-party authentication
- Suggested topics
- Summary
- Finalization and Deployment
- Switching to SQL Server
- Publishing our native web application
- Configuring the web server and IIS
- Firing up the engine
- Suggested topics
- Summary
Implementing the refresh token
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.