2
I would like to create a solution where I have 3 projects obeying the following structure:
The index of my site will be responsible for the registration of the user so that he has access to other systems (Webapp1 and Webapp2). But when I execute the registration and login in Identity and navigate to a page that requires authorization in Webapp1/ Confidential, the application is not considering the session that is already started and takes me to It is the user registration.
The goal is to separate my applications from the Identity layer. This would facilitate the management of projects and others that may arise.
At the moment I can not answer you with many details, but it seems to me that what you are looking for is an implementation of "Single Sign-On" (http://en.wikipedia.org/wiki/Single_sign-on). Try to search with this term, I think you will find more information.
– Conrad Clark
It would be something like SSO, but I want to be able to use Google, Facebook,... as logins and also an own registration, a standard MVC project with authentication. Webapp1 and Webapp2 (MVC Empty projects) are in the same domain and within the application (in IIS) of Identity. The problem is that the user already logged in (Identity) is not being taken into account within the other applications even being in the same domain. It must be a very basic need. I would not like but I’m thinking of using Areas in Identity and there I create Webapp1 and Webapp2.
– Onaiggac