Single Sign on Services for applications

SSO means a lot of things in different contexts.  

For example, I'm working on an SSO project for a client who has several public-facing web sites, each currently with an internal authentication and authorization provider, and they want to go to a single, shared authentication (but not authorization) provider, so that a customer can sign in once, and then using a shared "id", access resources on all of the related sites based on authorization rules stored in each site, without having to sign on separately.  We elected to use Azure AD B2C for this particular case.

Helpful if you can tell us about the use cases.  

What, specifically, do you mean by SSO?  

Who are the users?  

Typically, with SSO, you have to deal with authentication (Are you are who you say you are?) and optionally authorization (now that I know who you are, what are you allowed to do here?).  Do you need to handle authentication, authorization, or both?  

Any additional info you can provide will help us provide better guidance in terms of solutions.

Hello Gary, Thanks for your reply.

The 12 apps I mentioned are all web based services like dropbox, webex, universalbackground.com, and a few others. We are currently using Office 365 for email so perhaps its best to go the Azure route and keep it all in one place.

I'd like the users to login into one portal and have access to all of their apps from there without having to login again.

What do you mean by who are the users?

Internal users, external b2b users, or external b2c users.

Hello Gary, Yes it is for internal users that work from multiple locations through multiple states. There is no local domain controller but like I said before they are using Office 365 for email.

What, specifically, do you mean by SSO?  
Single sign-on (SSO) is a session and user authentication service that permits a user to use one set of login credentials (e.g., name and password) to access multiple applications.

Who are the users?  
The service authenticates the end user for all the applications the user has been given rights to and eliminates further prompts when the user switches applications during the same session. On the back end, SSO is helpful for logging user activities as well as monitoring user accounts.

Do you need to handle authentication, authorization, or both?  
We need to handle authentication for all users of applications.

@Tejas

Those questions were meant for the original poster, so that we could better understand the original request.

Traditional SSO requires all of the sites involved to trust a common authentication provider.  Office365, in particular makes it unlikely that all of the sites you are dealing will trust the same provider

You're probably going to have to look at some sort of SSO portal (onelogin, ventrify, etc) that takes a more active role in managing authentication than relying on a shared trust model. I have seen some, but I haven't evaluated them, and dont know exactly how they do what they do.  Maybe another expert can fill in some blanks.

I prefer you to use CloudCodes SSO Solution which is provide the best Single Sign-On solutions.
You can easily get associate multiple application with 100% cloud data security.