Single Sign On, two databases with their own identity tables RRS feed

  • Question

  • User-1978316082 posted

    Hi All,

    A client has a website that is using .net 4.0 with MVC. This website has its own database and identity tables.

    We implemented a web application for the client that is completely decoupled from the website and its database. The applications database holds session information of what the user did along with many other this linked to the user. The users interacts with a Web API to manipulate data and those actions are audited and mapped to the sessions which the administrator can run reports on.  This all works fine when the users are registered through the application itself and have their own login page which is how it was implemented at first.

    The problem is that now the client wants to have Single Sign On using the website login page. The client wants the login page removed from the application and allow every current and future user of the website to have access the web application.

    -What I know so far

    • Every user logging in through the website will have the Basic User Role in the application
    • The accounts that will have the Admin Role and Super Admin Role will be generated when the database is generated

    My question is:
    Is it possible to implement single sign on with two separate databases having their own identity tables? If it isn't what would be the best possible route to go since the application itself has its own authorization in place based on the specific users role and these users have been extended in the applications database. If it is possible what is the best way to get the existing users into the applications database if they aren't already in there.

    Any help to point me in the right direction is appreciated.

    Thank you,

    Thursday, November 12, 2015 1:21 PM