Last post Sep 28, 2016 11:46 AM by Yohann Lu
Sep 27, 2016 03:09 PM|hugonne|LINK
Here's the scenario: one of our clients has about 60 applications (and is in the process of creating some new ones), all in the same domain, and he wants to integrate authentication for all. So the basic requirement is to create (setup?) an "authentication
service" that would allow a user to sign on only to the first application. Of course this sounds as an SSO implementation, with the exception that we don't need to worry about multiple domains.
All authentication is for external users, so they don't need to integrate with AD (it's all Forms authentication). They do requiere to use a challenge/response mechanism for authentication, beacuse of a norm they have to compile to.
I've never actually done an implementation of something like this. I've used ASP.NET Identity in the past, but never to "integrate" several applications and share user information amongst them. I've looked into concepts like ADFS, Identity Server, STS, but
I'm not sure on what approach I should take here.
Any suggestions? Is it worth building something from scratch? Thanks a lot for your help.
Sep 28, 2016 11:46 AM|Yohann Lu|LINK
According to your description , As far as I know , you can achieve it by Single Sign on(SSO) . You log in main application , then you can access sub-applications without validate again .
For more details , Check out the following tutorials online:
Basics of Single Sign on (SSO):