Migrate your pages to .NET Core

The .NET Core Renderer does not limit you to create and edit only .NET Core pages. Using the Renderer, you can simultaneously work with .NET Core, MVC, and Web Forms pages. This means that in each site, you can have a mixed collection of all the three supported rendering mechanisms.
However, rendering .NET Core widgets in MVC or Web Forms based pages or vice versa is not possible.

This hybrid development approach helps you to migrate to .NET Core in the following scenarios:

• If you want to have all of your pages based on .NET Core, you do not have to migrate your site all together. Instead, you can do it one page at a time.
• If you want to leave all of your existing pages, based on their current framework and you want only your new pages to be based on .NET Core, you can create your new pages in .NET Core independently of your existing pages in MVC and Web Forms.

Having the Default or OpenID authentication protocol configured for Sitefinity, enables the Renderer and Sitefinity CMS to be in a Single Sing On (SSO) scenario, as well as Single Sign Out. This means that when you log in Sitefinity CMS, this automatically logs you in the Renderer app.
For example, the login form on an MVC-based page automatically logs the user to the .NET Core Renderer or vise versa.
The biggest benefit here is that when a user requests a .NET Core page the HttpContext.User property in the .NET Core Renderer app is properly configured with the ClaimsIdentity of the logged user. Because this is valid for only the GET requests that are related to rendering Sitefinity pages, if you want, you can to add it to any other request, such as form post to a custom controller.