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(275.2, 60%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
I've added the default Indentity pages for an .Net Core 8 Razor application and everything appears to be working fine with the Account pages.
My main question is how can I re-map the pages from "/Identity" to "/" (just for testing purposes for now)?
Currently:
Wanted:
I did try adding "app.MapGroup("/").MapIdentityApi<IdentityUser>();" after my "app.UseAuthorization();", but it didn't seem to do anything.
Is this the proper way of re-routing the pages? This MapGroup line didn't appear to make any difference.
Thanks,
Josh
What is the difference between "Currently:" and "Wanted:"?
Do you understand that "the Account pages" are not MVC but Razor Pages which routing is different from MVC?
I updated the title and description. What I have Currently is what it defaulted to when I added the Identity pages. Wanted is what I'd like the routing to be. I'm mostly familiar with attribute routing on MVC. Haven't done anything with Razor routing. Since it's Razor syntax, how can I adjust the routing?
![](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(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Microsoft identity is implemented as razor pages. It is hard coded to the area identity. It currently is not configurable. You will need to scaffold the pages and change their routing by editing the pages. you will also need to edit the login cookie options LoginPath and LogoutPath parameters to match.