Scott Reed
Nov 17, 2021
(2 votes)

Restore Root CMS episerver Login Path In .NET 5


With the release of CMS 12 there was the removal of dashboards which has caused the base login path to not work when created in a new project via the steps documented here 

Now with the out of the box code you have to navigate to /episerver/cms to access the CMS Editing area.

Although you can change the path to the CMS editing experience with the documented approach it does not work to change this to just /episerver as there needs to be a subpath for the CMS experience.


Using the ASP.NET Rewriting Middleware we can add a redirect to reirect /episerver to /episerver/cms

First add the nuget package

dotnet add package Microsoft.AspNetCore.Rewrite --version 2.2.0

Then add in the redirect to the Startup.cs configure code

var options = new RewriteOptions().AddRedirect("episerver$", "episerver/cms");


This is something simple but I've seen people confused therefore I wanted to post about it and propose an easy solution to remedy the problem. Ideally when you go to the root /episerver as everyone is used to doing you want to go to the CMS which this will do.

Also as a note now that Episerver is no longer the company name it strikes me odd to preserve it so I would follow the approach in anyhow and consider changing the default URL path to remove the old brand. Such as /cms/cms with a redirect from /cms &  /episerver to /cms/cms or any name of your choice :-) 

Happy coding!! Add any thoughts, errors or suggestions in the comments below!!

Nov 17, 2021


Please login to comment.
Latest blogs
Optimizely SendGrid SMTP host is deprecated

SendGrid is a services for sending email that is included in Optimizely DXP. Previously was the recommended SMTP server to use,...

Tomas Hensrud Gulla | Dec 4, 2022 | Syndicated blog

Hosting Optimizely CMS 12 on Docker Engine

Since Optimizely CMS can now be deployed as a Docker container, here is a demonstration of building, running and scaling an Optimizely CMS 12 site ...

Stefan Holm Olsen | Dec 4, 2022 | Syndicated blog

How to use CacheTagHelper with content areas in Optimizely CMS 12

I might be going out on a limb here - if you have a better solution, feel very free to share it!  Upgrading your Optimizely web application from .N...

Andreas J | Dec 2, 2022

The 1001st Piece in your 1000 Piece Puzzle: .NET Default Interface Functions

I was recently working with a client who wanted a reasonably large subsystem added to Optimizely that would add automated management to their...

Greg J | Nov 28, 2022 | Syndicated blog