Facilitate single sign-on between Asp.Net and Asp.Net Core 1.0 forms authentication using Framework

Question

We have several applications in one domain, and each application is built in asp.net mvc. Currently, single sign-on is facilitated by forms authentication, a shared machine key. At the moment, all applications are on the same server.

For our new application, we are considering asp.net core with a framework . We have an Accounts application that handles authentication (input / output) for an existing application. And we created STS using Identity Server3 in one application.

www.mydomain/Accounts www.mydomain/app1 www.mydomain/app2 www.mydomain/asp.netcoreApp1 

The new asp.net core test application (client) using openIdConnect communicates with STS, Identity Server3 and works fine.

Objective: Simplify single sign-on between existing forms-based authentication applications and the new Asp.Net Core.

Operational / environmental facts:

• All applications are on the same machine.

• Access to machine keys.

• When navigating from app1 to asp.net files, basic cookies are available in the request header.

Scenarios of problems:

• If the user has successfully connected to app1 and switched to the asp.net kernel, the user must again log in again for authorization. No problems with anonymous access.
• Similarly, # 1 is the opposite.
• If the user exits any application, the user must exit all applications.

Since the test application built using the Asp.net kernel with the framework parameter is compatible with FormsAuthentication? direct me to the documentation or code snippet?

Share your ideas.