Click here to Skip to main content
15,889,595 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
Hi, we currently have 2 web applications we want to create SSO service so that they and any other apps we create will have one web service (identity provider?) that will do the authentication. I am quite new to this so bare with my noobness.

Of the top of my head i can just create an internal web service (web api 2.0) that each web application can call to do that, and currently it will be internally called (everything hosted on same server). But I might need to move the web applications to different servers so security of that SSO service will be an issue.

Should I not be creating my own SSO and be using existing ones like OAuth? But most our clients will be usig their corporate emails they dont use their "social" accounts?

Any comments suggestions would be much appreciated.

thanx!
Posted
Updated 12-Mar-15 11:58am
v2

Ok, I figured it out. I basically want to implement OAuth or SAML, butt thats too hardcore for what I currently need , for now Ill just create an internal web service that does the authentication for all our web applications since we will be hosting them on the same server, but for fun ill prob try implementing OAuth 2.0 or SAML at home.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900