Authentication Protocols - Revision history

Tom: /* Solutions */

2018-11-09T00:26:48Z

‎Solutions

2018-07-12T04:40:15Z

‎Context

2018-07-12T04:33:38Z

‎Context

2018-07-12T04:32:43Z

‎Solutions

2018-07-12T04:30:17Z

‎Problems

2018-07-12T04:28:08Z

‎Problems

2018-07-12T04:26:23Z

‎Problems

2018-07-12T04:25:16Z

‎Federated or Open systems of users and services

2018-07-12T04:23:57Z

‎Captive users and services

2018-07-12T04:22:26Z

‎Context

@@ Line 26: / Line 26: @@
 [[Kerberos]]
-[[SAML]]
+[[SAML 2.0]]
 [[OpenID Connect]]

← Older revision		Revision as of 04:40, 12 July 2018
Line 13:		Line 13:

	In such an open system it is not often helpful for a user to be signed out of all web sites when they chose to sign out of (say) the purchase of concert tickets.		In such an open system it is not often helpful for a user to be signed out of all web sites when they chose to sign out of (say) the purchase of concert tickets.
		+
		+
		+	===Subsequent History===
		+	In the early 2000's Microsoft and other software providers began the process of linking

	==Problems==		==Problems==

@@ Line 3: / Line 3: @@
 ==Context==
-Since [[Kerberos]] was released at MIT in 1999 as a means to allow [[Single Sign On]] by students and staff to the variety of systems available at the university, the combination of one user sign on to a variety of different services has been promoted as necessary in the variety of network services now available to users. There are two distinct cases and a wide range of intermediate cases that are addressed by authentication protocols:
+Since [[Kerberos]] was released at MIT in 1999 as a means to allow [[Single Sign On]] by students and staff to the variety of systems available at the university. Since then the combination of one user sign on to a variety of different services has been promoted as necessary in the variety of network services now available to users. There are two distinct cases and a wide range of intermediate cases that are addressed by authentication protocols:
 ===Captive users and services===

@@ Line 17: / Line 17: @@
 * Users do not want to be forced to create a distinct sign-on user name and password (their credentials) at every site they visit.
 * It is proven to be insecure for users to be required to have distinct sign-on credentials as they will generally reuse their credentials at every site possible.
 ==Solutions==

@@ Line 15: / Line 15: @@
 ==Problems==
-Users doe not want to be forced to create a distinct sign-on user name and password at every site they visit.
+* Users do not want to be forced to create a distinct sign-on user name and password (their credentials) at every site they visit.
 ==Solutions==

← Older revision		Revision as of 04:26, 12 July 2018
Line 15:		Line 15:

	==Problems==		==Problems==
		+	Users doe not want to be forced to create a distinct sign-on user name and password at every site they visit.

	==Solutions==		==Solutions==

← Older revision		Revision as of 04:25, 12 July 2018
Line 11:		Line 11:

	===Federated or Open systems of users and services===		===Federated or Open systems of users and services===
		+
		+	In such an open system it is not often helpful for a user to be signed out of all web sites when they chose to sign out of (say) the purchase of concert tickets.

	==Problems==		==Problems==

@@ Line 7: / Line 7: @@
 ===Captive users and services===
 At MIT and at most corporations there is a pre-existing legal agreement that is signed by all users that applies to all services.
 ===Federated or Open systems of users and services===