Explore >> Select a destination
|
You are here 
|
brockallen.com | ||
| | | | |
weblog.west-wind.com
|
|
| | | | | In some situations you might need to use both Bearer Token and Cookie Authentication in a single application. In this post I look at a few scenarios where this is required and show how to configure your Authentication to let you access your site with either authentication scheme. | |
| | | | |
www.sjoerdlangkemper.nl
|
|
| | | | | Cookies are typically sent to third parties in cross origin requests. This can be abused to do CSRF attacks. Recently a new cookie attribute was proposed to disable third-party usage for some cookies, to prevent CSRF attacks. This post will describe the same-site cookie attribute and how it helps against CSRF. | |
| | | | |
timdeschryver.dev
|
|
| | | | | To improve the security of our Single Page Applications, let's ditch the access tokens in the browser and make the Backend for Frontend (BFF) responsible for the authentication process using the Authorization Code flow with PKCE. To achieve this, we'll use the Duende.BFF NuGet package and let it communicate with Auth0. | |
| | | | |
blog.peterritchie.com
|
|
| | | [AI summary] The author announces an open-source nuget package and project template that simplifies dependency injection and configuration management in .NET console applications. | ||
