Device Bound Session Credentials (DBSC) gan cookie phien vao khoa rieng tren thiet bi, khien cookie bi danh cap nhanh het gia tri. Bai viet nay giai thich cach DBSC hoat dong va ly do tinh nang nay da bi loai khoi .NET 11.
Cookie phien la mot bearer token. Noi don gian, ai nam giu cookie thi co the dong vai ban. Ke tan cong chi can sao chep cookie, gui lai no tu mot may khac va may chu van phuc vu tai khoan cua ban. Request khong co thong tin nao chung minh no den tu thiet bi nao, vi vay cookie bi lay boi malware, payload XSS hoac mot ban sao luu co so du lieu bi bo quen van co the tiep tuc hoat dong cho den khi het han. Neu phien co thoi gian song dai, khoang thoi gian nay co the keo dai nhieu tuan.
Device Bound Session Credentials la mot tieu chuan web dang duoc xay dung, nham xu ly dung khoang trong bao mat nay. .NET 11 tung co mot trien khai phia may chu mang tinh thu nghiem cho ASP.NET Core. Y tuong la gan phien voi mot khoa rieng khong bao gio roi khoi thiet bi, de cookie bi sao chep khong con du de duy tri phien.
Cap nhat thang 10 nam 2026: DBSC da bi rut khoi .NET 11. Nhom ASP.NET Core da loai bo trien khai nay sau RC1 vi no chua hoan thien va chua dat yeu cau mong muon; thay doi nay duoc dua nguoc vao RC2. Goi Microsoft.AspNetCore.Authentication.DeviceBoundSessions se khong duoc phat hanh cung ban .NET 11 chinh thuc. Ke hoach la lam lai tinh nang va co the dua no tro lai trong .NET 12. Ban co the theo doi dotnet/aspnetcore#66478. Phan giai thich giao thuc ben duoi van dung, nhung ma nguon chi hoat dong voi goi RC1.
Luu y: Ca phia trinh duyet va phia ASP.NET Core deu dang thu nghiem. Goi ASP.NET Core la goi prerelease trong toan bo vong doi .NET 11, con ho tro trinh duyet hien chi co tren Chrome voi co experimental. Day la tinh nang de tim hieu truoc va trien khai sau, khong phai thu ban nen xay dung va dua vao van hanh ngay hom nay.
Mục lục
Gan cap khoa cong khai va khoa rieng
Khi dang nhap, trinh duyet tao mot cap khoa cong khai va khoa rieng, sau do luu khoa rieng trong phan cung an toan. Neu thiet bi co Trusted Platform Module (TPM), khoa co the duoc luu tai do. Khoa cong khai duoc gui den may chu va gan voi phien. Khoa rieng van nam tren thiet bi va, tren may co TPM, khong the xuat ra ngoai.
Tu luc nay, phien dung cookie ngan han thay vi cookie dai han. Khi cookie het han, trinh duyet phai chung minh no van nam giu khoa rieng truoc khi may chu cap cookie moi. Ke tan cong sao chep cookie ngan han co the gui lai cookie cho den khi no het han, co the sau khoang muoi phut, nhung khong the lam moi cookie. Qua trinh lam moi can mot chu ky ma chi thiet bi goc moi tao duoc. Thoi gian su dung huu ich cua cookie bi danh cap vi the giam xuong bang thoi gian het han ngan han.
DBSC khong ngan chan viec cookie bi danh cap, nhung khien cookie danh cap nhanh tro nen vo dung hon.
Giao thuc Device Bound Session Credentials, ban rut gon
Phan lon endpoint trong ung dung ASP.NET Core khong can biet DBSC dang ton tai. DBSC xay dung tren co che xac thuc cookie ma ban dang su dung. Chi co hai diem moi: khi nguoi dung dang nhap va khi cookie ngan han can duoc lam moi.
Khi dang nhap, may chu tra ve cookie xac thuc thong thuong cung header Secure-Session-Registration, moi trinh duyet dang ky mot khoa. Voi tich hop ASP.NET Core thu nghiem, header nay duoc ghi khi ban dang nhap nguoi dung qua cookie scheme duoc boc lai:
HTTP/1.1 302 Found
Set-Cookie: .AspNetCore.Application=CfDJ8K...; path=/; samesite=lax; httponly
Secure-Session-Registration: (ES256 RS256);path="/.well-known/dbsc/registration";challenge="CfDJ8K..."
Neu thiet bi co the luu khoa, trinh duyet gui khoa cong khai den endpoint dang ky /.well-known/dbsc/registration. Handler tao endpoint nay, gan khoa voi phien va chuyen phien sang cookie ngan han. May chu tra ve cau hinh phien gom ma phien, URL lam moi va ten cookie duoc quan ly.
Khi cookie ngan han het han, trinh duyet tam dung request sap gui va goi endpoint lam moi de lay cookie moi. May chu tra ve mot challenge, trinh duyet ky challenge bang khoa rieng, sau do may chu kiem tra chu ky truoc khi cap cookie ngan han moi. Chi sau do request ban dau moi tiep tuc. Voi nguoi dung, moi viec dien ra nhu khong co gi xay ra.
Diem de ap dung la cac endpoint thong thuong van lam viec nhu cu: kiem tra cookie xac thuc hop le. DBSC la mot lop bo sung; no thay doi cach cookie duoc lam moi, khong thay doi cach ung dung doc va su dung cookie.
Ban chung co chu ky thuc su la gi?
Ta thuong noi rang trinh duyet ky challenge roi bo qua chi tiet. Hieu ro chu ky nay cho thay vi sao cookie bi sao chep khong the bi phat lai.
Ban chung la mot JSON Web Token duoc ky bang khoa rieng cua thiet bi. Header cho biet thuat toan (ES256, RS256, hoac none neu ban tu bo y nghia bao mat cua tinh nang). Trong luc dang ky, header con chua public key duoi dang JWK. Nho vay, may chu nhan duoc khoa tu ban chung dang ky da duoc ky. Payload gan nhu rong; claim quan trong la jti, ban sao cua challenge ma may chu vua phat:
// header
{
"alg": "ES256",
"typ": "dbsc+jwt",
"jwk": { "kty": "EC", "crv": "P-256", "x": "...", "y": "..." }
}
// payload
{
"jti": "the-challenge-your-server-issued"
}
Trong qua trinh lam moi, cau truc van giong vay nhung khong con jwk, vi may chu da co khoa cong khai tu luc dang ky. May chu gui challenge moi, trinh duyet ky token moi voi challenge nam trong jti, va may chu kiem tra hai dieu: chu ky co xac thuc duoc bang khoa cong khai hay khong, va jti co phai la challenge ma may chu vua cap hay khong.
Challenge la mot nonce ngan han do may chu tao ra, vi vay ban chung chi co gia tri cho mot lan lam moi duy nhat. Neu ke tan cong thu duoc ban chung cu, ho khong the lam gi voi no vi jti da cu va may chu se tu choi. Day la diem khac nhau giua proof of possession va bearer token: thay vi nam giu mot gia tri co the tiep tuc hoat dong, ban phai moi lan ky mot gia tri moi bang khoa khong the sao chep.
Chu ky duoc tao ben trong TPM, vi vay ngay ca ma dang chay voi quyen tuong ung tren may cung khong the doc khoa rieng ra ngoai. Ma doc hai van co the yeu cau TPM ky trong khi khoa dang nam tren may; day chinh la lo hong khi malware da co mat trong luc dang ky. Tuy nhien, malware khong the mang khoa di noi khac de su dung. DBSC dat ra ranh gioi nay: cuoc tan cong phai tiep tuc o cuc bo va de bi phat hien, thay vi am tham tai su dung vinh vien.
Cau hinh Device Bound Session Credentials trong ASP.NET Core
.NET 11 RC1 bo sung phan phia may chu cua DBSC trong goi Microsoft.AspNetCore.Authentication.DeviceBoundSessions. Day la goi prerelease, vi vay can them tuy chon --prerelease:
dotnet add package Microsoft.AspNetCore.Authentication.DeviceBoundSessions --prerelease
DBSC bo sung tren mot cookie authentication scheme co san. Ban dang ky cookie auth nhu thuong le, sau do noi AddDeviceBoundSession vao cung ten scheme:
var builder = WebApplication.CreateBuilder(args);
builder.Services
.AddAuthentication("Application")
.AddCookie("Application")
.AddDeviceBoundSession("Application", options =>
{
// Thoi gian cookie phien duoc quan ly ton tai truoc khi
// trinh duyet phai chung minh quyen so huu khoa de lam moi.
options.ShortLivedCookieExpiration = TimeSpan.FromMinutes(10);
});
builder.Services.AddAuthorization();
var app = builder.Build();
app.UseAuthentication();
app.UseAuthorization();
app.MapGet("/", (HttpContext context) =>
$"Hello {context.User.Identity?.Name ?? "anonymous"}")
.RequireAuthorization();
app.Run();
Gan nhu chi can vay. Ma xac thuc cua ban khong thay doi: sau khi kiem tra thong tin dang nhap, ban van goi HttpContext.SignInAsync("Application", principal). DBSC handler boc scheme nay, gui header dang ky, tao endpoint dang ky va lam moi, quan ly cookie lam moi gioi han theo path, dong thoi xoay vong cookie phien ngan han.
ShortLivedCookieExpiration la tuy chon cau hinh chinh co the dieu chinh. Gia tri ngan hon khien cookie bi danh cap het han som hon, nhung cung lam tang so lan trao doi lam moi va so lan TPM phai ky. TPM duoc dung chung tren toan bo he thong va co gioi han tan suat, vi vay gia tri thap hon khong tu dong tot hon. Day la can bang giua muc do an toan va tan suat thiet bi phai ky challenge.
May chu luu khoa cong khai o dau?
May chu phai ghi nho khoa cong khai cua tung phien de xac minh cac lan lam moi sau nay. Tuy nhien, trong mau cau hinh khong co co so du lieu, distributed cache hay session store nao. Vay khoa duoc luu o dau?
Xem ma nguon, cau tra loi la “nhieu cookie hon” ket hop voi ASP.NET Core Data Protection.
AddDeviceBoundSession nam tren ba cookie scheme: cookie dang nhap goc, cookie phien ngan han va cookie lam moi gioi han theo path. Khi dang ky, handler doc khoa cong khai tu proof JWT va them no vao authentication properties cua cookie lam moi:
refreshProperties.Items["DbscPublicKeyJwk"] = jwtResult.PublicKeyJwk;
refreshProperties.Items["DbscSessionId"] = sessionId;
await Context.SignInAsync(Options.RefreshScheme, principal, refreshProperties);
Cac item nay duoc serialize vao cookie ticket va ma hoa bang Data Protection, nen khoa cong khai nam ben trong cookie lam moi HttpOnly da ma hoa. O lan lam moi tiep theo, handler xac thuc cookie nay va doc khoa tro lai. Client mang theo thong tin khoa ma may chu can, nhung khong the doc hay sua doi no vi khoa da duoc ma hoa bang mot khoa chi may chu nam giu.
Challenge cung hoat dong theo cach tuong tu. Thay vi ghi nho danh sach nonce da cap, challenge protector tao moi challenge duoi dang token Data Protection co thoi han, ma hoa danh tinh nguoi dung va ma phien. Khi xac minh, he thong giai ma token va kiem tra cac truong nay, nen khong can danh sach luu tren may chu de biet “challenge nay gan day co phai do minh cap khong”. Dang ky va lam moi con dung cac Data Protection purpose rieng, vi vay challenge cua luong nay khong the duoc giai ma boi luong kia.
Uu diem la mo rong qua nhieu may chu ma khong can session state dung chung, mien la cac khoa Data Protection duoc dung chung. Day cung la yeu cau ma cookie authentication von da co. Cach nay cung khong co session store de ke tan cong bom day session rac: kho luu tru dua tren co so du lieu se tang theo moi lan dang ky va can duoc bao quan, don dep; trong mo hinh nay, moi phien nam trong cookie cua chinh client.
Mat trai la thu hoi phien. Khi khong co bang phien, ban khong co nut don gian de “huy phien X”. Neu can kha nang nay, ban phai tu theo doi phien va xu ly viec thu hoi vao lan lam moi tiep theo.
Tom tat
Device Bound Session Credentials mang lai kha nang bao ve co y nghia truoc viec phat lai phien, gan nhu khong can thay doi ma ung dung, tren nen cookie scheme ma ban da su dung. Khi phan cung hoac trinh duyet khong ho tro, DBSC quay ve cach hoat dong cookie tieu chuan, nen nguoi dung khong bi khoa khoi he thong.
Tuy vay, DBSC van co gioi han. Phia trinh duyet hien chi ho tro Chrome va phai bat co experimental, vi vay hay xem DBSC la lop nang cao cho cac client tuong thich, khong phai co che kiem soat co the ap dung cho tat ca nguoi dung. DBSC chi hoat dong qua HTTPS. No cung khong phai phep mau truoc mot may bi xam pham: neu malware da co mat trong luc dang ky, no co the lay duoc khoa, va khi do ban quay lai tinh huong cookie co the bi danh cap nhu binh thuong. DBSC lam tang chi phi tan cong, nhung khong xoa bo moi de doa.
Hay theo doi DBSC tu bay gio va can nhac su dung khi ho tro tu trinh duyet da san sang.



