Hi all, I would just like to confirm, it seems that setting the Umbraco path is no longer possible in Umbraco 10+? I can't find any mention of it but the source seems unambiguous:

/// <summary>
///     Gets or sets a value for the Umbraco back-office path.
/// </summary>
public string UmbracoPath
{
    get => Constants.System.DefaultUmbracoPath;
    [Obsolete($"{nameof(UmbracoPath)}  is no longer configurable, property setter is scheduled for removal in V12")]
    // NOTE: when removing this, also clean up the hardcoded removal of UmbracoPath in UmbracoJsonSchemaGenerator
    set { }
}

That is correct

I think you can just use middleware for that instead

I was wondering about that but I can't think off hand how I'd do it. I'll investigate further if it becomes a sticking point

You can use rewrite middleware. There you go https://learn.microsoft.com/en-us/aspnet/core/fundamentals/url-rewriting?view=aspnetcore-7.0

I was just reading this, thanks!

Just to note, I haven't tried the middleware solution but we have not found a way to make the umbraco path configurable again, our current advise is to lock it down with IP restrictions (which we realize is far from ideal). https://github.com/umbraco/Umbraco-CMS/issues/12593#issuecomment-1607150190 Changing the path is definitely going to cause unexpected and surprising things to happen since neither Umbraco itself nor any package expect the path to be anything else. So, do give it a try but don't be surprised if things start breaking fairly quickly after that. 🙈