<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/experimental-support-for-device-bound-session-credentials-dbsc-in-asp-net-core-naljsvdwm" -->

---
title: Experimental support for Device Bound Session...
description: A deep dive into the new experimental Device Bound Session Credentials (DBSC) support shipped for .NET 11 in the...
canonical: https://daily.dev/posts/experimental-support-for-device-bound-session-credentials-dbsc-in-asp-net-core-naljsvdwm
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Experimental support for Device Bound Session Credentials (DBSC) in ASP.NET Core | daily.dev
og:description: A deep dive into the new experimental Device Bound Session Credentials (DBSC) support shipped for .NET 11 in the...
og:url: https://daily.dev/posts/experimental-support-for-device-bound-session-credentials-dbsc-in-asp-net-core-naljsvdwm
og:image: https://api.daily.dev/og/posts/nALJsvdWM.png
og:image:alt: Experimental support for Device Bound Session Credentials (DBSC) in ASP.NET Core
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Experimental support for Device Bound Session Credentials (DBSC) in ASP.NET Core

**[.NET Escapades](https://daily.dev/sources/andrewlock)** · 15 min read · 3 upvotes · 0 comments

## Summary

A deep dive into the new experimental Device Bound Session Credentials (DBSC) support shipped for .NET 11 in the Microsoft.AspNetCore.Authentication.DeviceBoundSessions NuGet package. DBSC defends against cookie theft by binding refresh tokens to a device-held private key stored in a TPM, replacing long-lived cookies with short-lived ones after a registration handshake. The walkthrough shows wiring DBSC into an ASP.NET Core Identity app via AddDeviceBoundSession(), covers the internal cookie schemes, policy scheme handler, and PostConfigureOptions classes involved, and traces the actual HTTP registration and refresh exchanges using server logs since Chrome hides these requests from DevTools. The feature remains experimental throughout .NET 11 but requires minimal code to try.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://andrewlock.net/exploring-the-dotnet-11-preview-8-experimental-support-for-device-bound-session-credentials-in-aspnetcore>

## Questions this post answers

### How do I enable Device Bound Session Credentials (DBSC) in an ASP.NET Core app using .NET 11?

Install the Microsoft.AspNetCore.Authentication.DeviceBoundSessions preview package with the --prerelease flag, then call AddDeviceBoundSession("SchemeName") on the AuthenticationBuilder after configuring your cookie scheme, passing the name of the cookie scheme to protect. For ASP.NET Core Identity apps, wrap the builder.Services in a new AuthenticationBuilder and call AddDeviceBoundSession(sourceScheme: IdentityConstants.ApplicationScheme) since AddDefaultIdentity hides the normal chaining call.

_See daily.dev for more on hardening ASP.NET Core authentication with the latest .NET 11 features._

### Why can't I see the DBSC registration and refresh requests in Chrome's network tab?

Chrome deliberately hides DBSC registration and refresh requests from the normal network tab, so testing requires checking server-side logs instead. Enabling Information-level ASP.NET Core infrastructure logging in appsettings.json reveals the POST requests to /.well-known/dbsc/registration and /.well-known/dbsc/refresh along with the cookie sign-in events. Chrome does expose a separate 'Device bound sessions' tab showing whether a session is active.

_Developers debugging DBSC flows can track these ASP.NET Core security changes on daily.dev._

### Why is my DBSC session not registering when I test it in the browser?

DBSC only activates when the app is served over HTTPS, so ensure the https launch profile runs first or is used explicitly, and trust the dev certificate with dotnet dev-certs https --trust. Ad blockers can also prevent DBSC from working entirely, so disabling them during testing is necessary since the registration handshake fails silently otherwise.

_daily.dev helps developers stay on top of tricky new browser security protocols like DBSC._

## Similar posts on daily.dev

- [Understanding Device Bound Session Credentials \(DBSC\)](https://daily.dev/posts/understanding-device-bound-session-credentials-dbsc--lenaynz6n) · .NET Escapades · 0 upvotes · 0 comments
- [Device Bound Session Credentials now available on Windows](https://daily.dev/posts/device-bound-session-credentials-now-available-on-windows-z7l2wmrgc) · Chrome Developers · 3 upvotes · 0 comments
- [Device Bound Session Credentials: Making Stolen Cookies Useless](https://daily.dev/posts/device-bound-session-credentials-making-stolen-cookies-useless-umty3wgjt) · Scott Helme · 0 upvotes · 0 comments
- [Google Chrome adds session cookie theft protection for all users](https://daily.dev/posts/google-chrome-adds-session-cookie-theft-protection-for-all-users-hmsdzdl44) · BleepingComputer · 36 upvotes · 9 comments

---

Tags: [#aspnet](https://daily.dev/tags/aspnet)

[View this post on daily.dev](https://daily.dev/posts/experimental-support-for-device-bound-session-credentials-dbsc-in-asp-net-core-naljsvdwm)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Experimental support for Device Bound Session Credentials (DBSC) in ASP.NET Core","url":"https://daily.dev/posts/experimental-support-for-device-bound-session-credentials-dbsc-in-asp-net-core-naljsvdwm","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/experimental-support-for-device-bound-session-credentials-dbsc-in-asp-net-core-naljsvdwm"},"datePublished":"2026-09-22T10:23:24.217Z","dateModified":"2026-09-22T10:23:47.356Z","description":"A deep dive into the new experimental Device Bound Session Credentials (DBSC) support shipped for .NET 11 in the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a00db338a68e8acb15d3b03cf59be2e7?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a00db338a68e8acb15d3b03cf59be2e7?_a=AQAEuop","isAccessibleForFree":true,"articleSection":".NET Escapades","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":".NET Escapades","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/74ebd66cf7e840b6b29913eae3da9189","url":"https://daily.dev/sources/andrewlock"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/experimental-support-for-device-bound-session-credentials-dbsc-in-asp-net-core-naljsvdwm","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"aspnet","timeRequired":"PT15M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":".NET Escapades","item":"https://daily.dev/sources/andrewlock"},{"@type":"ListItem","position":3,"name":"Experimental support for Device Bound Session Credentials (DBSC) in ASP.NET Core"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/experimental-support-for-device-bound-session-credentials-dbsc-in-asp-net-core-naljsvdwm#faq","mainEntity":[{"@type":"Question","name":"How do I enable Device Bound Session Credentials (DBSC) in an ASP.NET Core app using .NET 11?","acceptedAnswer":{"@type":"Answer","text":"Install the Microsoft.AspNetCore.Authentication.DeviceBoundSessions preview package with the --prerelease flag, then call AddDeviceBoundSession(\"SchemeName\") on the AuthenticationBuilder after configuring your cookie scheme, passing the name of the cookie scheme to protect. For ASP.NET Core Identity apps, wrap the builder.Services in a new AuthenticationBuilder and call AddDeviceBoundSession(sourceScheme: IdentityConstants.ApplicationScheme) since AddDefaultIdentity hides the normal chaining call. See daily.dev for more on hardening ASP.NET Core authentication with the latest .NET 11 features."}},{"@type":"Question","name":"Why can't I see the DBSC registration and refresh requests in Chrome's network tab?","acceptedAnswer":{"@type":"Answer","text":"Chrome deliberately hides DBSC registration and refresh requests from the normal network tab, so testing requires checking server-side logs instead. Enabling Information-level ASP.NET Core infrastructure logging in appsettings.json reveals the POST requests to /.well-known/dbsc/registration and /.well-known/dbsc/refresh along with the cookie sign-in events. Chrome does expose a separate 'Device bound sessions' tab showing whether a session is active. Developers debugging DBSC flows can track these ASP.NET Core security changes on daily.dev."}},{"@type":"Question","name":"Why is my DBSC session not registering when I test it in the browser?","acceptedAnswer":{"@type":"Answer","text":"DBSC only activates when the app is served over HTTPS, so ensure the https launch profile runs first or is used explicitly, and trust the dev certificate with dotnet dev-certs https --trust. Ad blockers can also prevent DBSC from working entirely, so disabling them during testing is necessary since the registration handshake fails silently otherwise. daily.dev helps developers stay on top of tricky new browser security protocols like DBSC."}}]}
```

