Future Plans - Revision history

Dirk: some status updates

2010-10-29T20:25:21Z

some status updates

Dirk: link to FR #950

2010-02-10T15:45:26Z

link to FR #950

Dirk: there's also a login form on auth.inc.php

2010-02-10T15:43:36Z

there's also a login form on auth.inc.php

Dirk: one possible requirement for a kses replacement

2010-01-17T21:24:28Z

one possible requirement for a kses replacement

Dirk: minor updates and additions

2009-05-15T12:59:51Z

minor updates and additions

Dirk: OAuth

2008-08-21T09:23:33Z

OAuth

Dirk: Microformats

2008-08-13T15:47:17Z

Microformats

Dirk: Output compression

2008-08-12T08:56:07Z

Output compression

Dirk: HTTP Digest Authentication

2008-08-12T08:55:06Z

HTTP Digest Authentication

Dirk: Need a list of requirements for a new HTML filter

2008-08-08T15:10:49Z

Need a list of requirements for a new HTML filter

@@ Line 12: / Line 12: @@
 * Clean up user preferences ("My Account") for remote users: Hide options that are not available (e.g. password change)
 * Also: [[SoC full openid support|Support for OpenID 2.0]] would be nice (Geeklog 1.5.0 supports OpenID 1.1)
@@ Line 21: / Line 24: @@
 * Ability to allow config access for certain user groups (currently [http://project.geeklog.net/tracking/view.php?id=950 requires Root access] for everything)
 * Searching for a setting
@@ Line 42: / Line 47: @@
 ==== OAuth ====
-Would [http://oauth.net/ OAuth] help?
+Would [http://oauth.net/ OAuth] help? Also see [http://project.geeklog.net/tracking/view.php?id=1191 feature request #1191]
 === HTML filter ===
@@ Line 54: / Line 59: @@
 Candidates:
 * [http://htmlpurifier.org/ HTML Purifier]

@@ Line 19: / Line 19: @@
 * Re-ordering / re-grouping of options
-* Ability to allow config access for certain user groups (currently requires Root access for everything)
+* Ability to allow config access for certain user groups (currently [http://project.geeklog.net/tracking/view.php?id=950 requires Root access] for everything)
 * Searching for a setting

@@ Line 8: / Line 8: @@
 * Missing email addresses
 * Ability to make remote users "local" users (and vice versa)
-* Need to clean up and unify / merge the login forms (side block and users.php)
+* Need to clean up and unify / merge the login forms (side block, users.php, auth.inc.php)
 * Ability to re-sync data with remote auth service, e.g. change of email address
 * Clean up user preferences ("My Account") for remote users: Hide options that are not available (e.g. password change)

@@ Line 50: / Line 50: @@
 Requirements:
 * ??? (tbd)
 Candidates:

@@ Line 3: / Line 3: @@
 == Clean up Remote Authentication ==
-With the addition of OpenID and LDAP support in Geeklog 1.5.0, remote users will become more common and existing problems will become more apparent. For example:
+With the addition of [[OpenID]] and [[LDAP Remote Authentication|LDAP]] support in Geeklog 1.5.0, remote users will become more common and existing problems will become more apparent. For example:
 * Duplicate email addresses
@@ Line 9: / Line 9: @@
 * Ability to make remote users "local" users (and vice versa)
 * Need to clean up and unify / merge the login forms (side block and users.php)
 * Ability to re-sync data with remote auth service, e.g. change of email address
 * Clean up user preferences ("My Account") for remote users: Hide options that are not available (e.g. password change)
-* Also: Support for OpenID 2.0 would be nice (Geeklog 1.5.0 supports OpenID 1.1)
+* Also: [[SoC full openid support|Support for OpenID 2.0]] would be nice (Geeklog 1.5.0 supports OpenID 1.1)
@@ Line 21: / Line 20: @@
 * Re-ordering / re-grouping of options
 * Ability to allow config access for certain user groups (currently requires Root access for everything)
@@ Line 65: / Line 65: @@
 ** 403 Access denied (obvious; already used in some places)
 ** 409 Conflict (e.g. when something already exists)
-** 500 Internal Server Errror (sounds like we should send that whenever we display "Unfortunately an error occured ...")
+** 500 Internal Server Errror (already used for "Unfortunately an error occured ..." - where else?)
 * Make use of <tt>Last-Modified:</tt> header (where is this actually possible?)
 === Microformats ===
 Somewhat related: Look into using (more) [http://microformats.org/ Microformats]
 [[Category:Development]]

← Older revision		Revision as of 09:23, 21 August 2008
Line 39:		Line 39:

	Alternatively (instead of WSSE), if we wanted to support HTTP Digest Authentication, we would only have to keep track of the <tt>(user:realm:password)</tt> hash, probably as a separate field in the <tt>gl_users</tt> table, that needs to be updated whenever one of the three elements changes.		Alternatively (instead of WSSE), if we wanted to support HTTP Digest Authentication, we would only have to keep track of the <tt>(user:realm:password)</tt> hash, probably as a separate field in the <tt>gl_users</tt> table, that needs to be updated whenever one of the three elements changes.
		+
		+	==== OAuth ====
		+
		+	Would [http://oauth.net/ OAuth] help?

	=== HTML filter ===		=== HTML filter ===

← Older revision		Revision as of 08:55, 12 August 2008
Line 35:		Line 35:

	Somewhat related: If we wanted to support WSSE for the [[Webservices API#Authentication\|Webservices]], we would either need to store the user's password in a way that's secure but reversible (so that we can get the unencrypted password for use in WSSE authentication) or think of a way to create a token / temp. password that the user can use in WSSE authentication.		Somewhat related: If we wanted to support WSSE for the [[Webservices API#Authentication\|Webservices]], we would either need to store the user's password in a way that's secure but reversible (so that we can get the unencrypted password for use in WSSE authentication) or think of a way to create a token / temp. password that the user can use in WSSE authentication.
		+
		+	==== HTTP Digest Authentication ====
		+
		+	Alternatively (instead of WSSE), if we wanted to support HTTP Digest Authentication, we would only have to keep track of the <tt>(user:realm:password)</tt> hash, probably as a separate field in the <tt>gl_users</tt> table, that needs to be updated whenever one of the three elements changes.

	=== HTML filter ===		=== HTML filter ===

← Older revision		Revision as of 15:10, 8 August 2008
Line 39:		Line 39:

	Since kses is no longer maintained, we need a replacement.		Since kses is no longer maintained, we need a replacement.
		+
		+	Requirements:
		+	* ??? (tbd)

	Candidates:		Candidates: