This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 65%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZH%3C/text%3E%3C/svg%3E)
I wanna hide that i use ASP.NET Core.
How to do this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
Can you not just set the cookie name as part of your AddAuthentication call?
csharp
services.AddAuthentication()
.AddCookie(options => {
options.CookieName = "MyAuth.Cookie"
});
This method didn't worked in my project.
I'm working on dotnet core version 5.0.1 environment.
You are code is maybe work on dotnet core version 2.x.
I solved this problem.
This is my code.
.
.
.
using Microsoft.Extensions.DependencyInjection;
.
.
.
namespace MyProject
{
public class Startup
{
.
.
.
public void ConfigureServices(IServiceCollection services)
{
.
.
.
services.ConfigureApplicationCookie(options =>
{
options.Cookie.Name = "MyCustomCookieName";
});
.
.
.
}
.
.
.
}
}
.NET 5 is just .NET Core 4 renamed to avoid confusion. What is the cookie name you're seeing?
This is The DevTool Window that my seeing in Chrome.
It is working fine for me. Changing the Cookie.Name property correctly replaces AspNetCore.Identity.Application. But there could be a couple of things going on here so you should verify. Firstly if you have any sort of persistence option in the browser then the cookie will persist across sessions. Therefore if you had used the original cookie name, changed the name in code and then reran the app then you'd see both the old and new cookie. Clear your cookies for the site after changing the name and then log back into the site. The default cookie name should be gone.
I will say that changing the cookie name will not hide that you're using ASP.NET Core. There are other (unchangeable) cookies that indicate Core. From a security standpoint it does make sense to limit server info but it probably isn't going to change an attackers approach that much. I would only change the cookie for SSO purposes myself.
Thanks to your answer cooldadtx.
I cleared cookies. But, The cookie what had new name was didn't generated.
Ok, I will try it one more time as you said.
And, As far as I know, ASP.NET Core has default one cookie and has one more cookie, if i used the identity.
I modified the default cookie name already and cookie of identity in a few ago too.
The why i used individual authentication is which my project is inner system on my company.
I learned another way thanks to your hard.
Thank you cooldadtx.
ASP.NET Core has more than one cookie. If you're building an MVC app then the anti forgery cookie is named with aspnetcore. Other components will do this as well. You can see this by creating a new ASP.NET Core 5 app with user auth and MVC. I'm seeing 3 aspnet cookies just by logging in. For reference here's the auto-generated startup code with the cookie name change and what I see in the browser.
csharp
//After services.AddDefaultIdentity()...
services.ConfigureApplicationCookie(options => options.Cookie.Name = "TestApp");
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 35%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHH%3C/text%3E%3C/svg%3E)
I dont know why but you cant rename cookie name with AddCookie(options...) you have to do
builder.Services.ConfigureApplicationCookie(opt =>{
opt.Cookie.Name = "YourCookieName";
});