Manual approval of new users under jetspeed

[Chris Kimpton <ki...@yahoo.com>]

Hi,

Is there a facility to have a manual approval step in the user
creation process?

Would this be an acceptable patch to jetspeed?

I imagine it would be an optional feature, that is off by default. 
You'd configure it in the jetspeedresources.properties - perhaps by
supplying an email address for the approver.

This would then include the confirmation link, so that the user can
be authorised - and probably a reject link too.

In either case, an email would be sent to the user, notifying them of
the decision.

Alternatively/additionally this could be done through the user admin
portlet - with accept/reject links next to each un-approved user.  I
guess the existing confirm_value column could be used to hold this
information - pending/accepted/rejected - although a new column would
probably be the best route.

Regards,
Chris

=====
Need somewhere to Live in London - http://freeflats.com

__________________________________________________
Do You Yahoo!?
NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

Re: Manual approval of new users under jetspeed

[Santiago Gala <sg...@hisitech.com>]

Chris Kimpton wrote:

>Hi,
>
>Is there a facility to have a manual approval step in the user
>creation process?
>
>Would this be an acceptable patch to jetspeed?
>
+1.

>
>I imagine it would be an optional feature, that is off by default. 
>You'd configure it in the jetspeedresources.properties - perhaps by
>supplying an email address for the approver.
>
>This would then include the confirmation link, so that the user can
>be authorised - and probably a reject link too.
>
>In either case, an email would be sent to the user, notifying them of
>the decision.
>
>Alternatively/additionally this could be done through the user admin
>portlet - with accept/reject links next to each un-approved user.  I
>guess the existing confirm_value column could be used to hold this
>information - pending/accepted/rejected - although a new column would
>probably be the best route.
>
A new column would require changing the session validation scheme, while 
pending/CONFIRMED/rejected should work (notice the change) with the 
current validator, as it only looks for CONFIRMED in this field.

>
>Regards,
>Chris
>
>=====
>Need somewhere to Live in London - http://freeflats.com
>
>__________________________________________________
>Do You Yahoo!?
>NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
>http://geocities.yahoo.com/ps/info1
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>




---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org