OpenID, OpenSSO and OAuth -

My understanding of OpenID is that it is a site that includes all of your identities and identities. Peripheral information, but other open-end-compatible (and user-trusted) sites allow the user to reuse that information to identify and authenticate. Originally it reduces the number of login credentials (user name and password) for a consumer to the Internet.

My understanding of OpenSSO is that it allows you to sign-in on one site and automatically log in. All other sites that rely on the first site are basically users Reduces the number of logging in to these individual sites.

My understanding of OAuth is that it allows users to provide third party sites access to their information located on a particular site. Essentially, unlike OpenSSO, it reduces the number of users logging in to these different sites. Unlike OpenSSO, the OpenSSO logs the user in all affiliate sites (current with full privileges) at once , While Oeth provides better access to participating sites.

So, in advance, whatever I said is wrong, please start by correcting me!

Say I am more or less right, then clarification is required on the following questions:

• When I will choose OpenSSO on OAuth - just when I Want to restrict access which is in other affiliate sites, when the user logs any of them?
• Do they have different safety risks for each of these techniques? I have to consider and integrate my app - or they are considered safe and myself (Basically I can be assured that if my app uses them, then my app is not open to any new attacks)?

  Since these technologies are so closely connected because I see the whole "eagle through the tree" - thanks in advance!

  Actually do not have to compare correctly. OpenID & amp; OAIT protocol, OpenSSO (now OpenM) is an implementation of those and other protocols (SAML, OAuth, etc.). Generally, the protocols for OpenID and Oath are the same, although they have arisen from different usage cases in the brain. Today there is a lot of convergence around Oath 2.0 for both the Federation (Authentication) and the Authority Cases. The next generation of OpenID is built on top of Oath 2.0 and already already exists in Google, Facebook, Twitter, etc. ...

  For security, there are always some risks, especially Choose a good implementation with implementation errors and read the specs so that you understand what the risks and counterreactions are.