[OPEN-ILS-GENERAL] Password Reset feature

Tue Jul 13 10:52:48 EDT 2010

One other minor note: The form template reset-dorm.tt2 in .../templates/password-reset/ worked well in Chromium and Chrome out of the box, but did not work in IE8 or Firefox 3.5 (Ubuntu) or Firefox 3.6 (Windows). I added an old style form submit button so I can now reset my password from all browsers I tested.

Thanks,
Robert

-----Original Message-----
From: open-ils-general-bounces at list.georgialibraries.org [mailto:open-ils-general-bounces at list.georgialibraries.org] On Behalf Of Soulliere, Robert
Sent: Saturday, July 10, 2010 9:02 AM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] Password Reset feature

Thanks Dan!

I was able to complete the entire process and changed my password from the OPAC.

The other variable in my mangled system is that our database already has the booking module schema and tables since we have been using the booking module since February. Would this be the cause of the 1.6.1.0 upgrade script choking out since it would try to create a schema and tables that already exist?

I really appreciate your help, especially since I am working with 1.6.1.1 which hasn't been officially released yet.

Regards,
Robert

________________________________________
From: open-ils-general-bounces at list.georgialibraries.org [open-ils-general-bounces at list.georgialibraries.org] On Behalf Of Dan Scott [dan at coffeecode.net]
Sent: July 10, 2010 3:52 AM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] Password Reset feature

On Fri, 2010-07-09 at 22:23 -0400, Soulliere, Robert wrote:
> After digging into the logs a little deeper, I have the first step figured out and the requests are getting through and populating the necessary database tables.
>
> It turned out that the upgrade sql for 1.6.1.0 didn't completely run so the required tables for the password reset were not created and the action trigger entries were not added. I added those using a part of the upgrade script.

It would be good to figure out if the upgrade SQL didn't run because of
your mangled half-upgrade/half-install approach or because of a real
problem with the upgrade script. I'll admit that when you wrote that
your upgrade mixed an operating system upgrade (and presumably a
database upgrade) along with the Evergreen upgrade and that things
weren't necessarily working properly, I wasn't enthusiastic about trying
to help out. More than one variable at a time == messy.

But now that you've got this far, I can help with the action trigger
bit.

> Now, I will look into the action trigger part to send the reset email.
>

Okay.

First, delete all entries from your actor.usr_password_reset table.

Second, ensure that the action trigger event definition for the password
reset notification is enabled. It's disabled by default, like all
events, so you need to turn it on.

Third, request a password reset for a user who has an email address.
This will populate both the actor.usr_password_reset table and the
action_trigger.event table with a row.

Fourth, run "action_trigger_runner.pl --process-hooks --run-pending
--debug-stdout" to generate the email notice. The "--debug-stdout" is
only necessary when you're initially testing things out; once you put
the command into a cron job you can forget about it.

You'll probably want to adjust the template for the email in the action
trigger event definition; for example, you should add your library's
hostname so that the embedded link will actually resolve for your users.
But this should get you going.

Oh, and there are a few library settings that affect password resets
that you might want to look at, depending on your needs:

  * circ.password_reset_request_per_user_limit: Maximum concurrently
active self-serve password reset requests per user. When a user has more
than this number of concurrently active self-serve password reset
requests for their account, prevent the user from creating any new
self-serve password reset requests until the number of active requests
for the user drops back below this number.

  * circ.password_reset_request_time_to_live: Self-serve password reset
request time-to-live. Length of time (in seconds) a self-serve password
reset request should remain active.

  * circ.password_reset_request_throttle: Maximum concurrently active
self-serve password reset requests. Prevent the creation of new
self-serve password reset requests until the number of active requests
drops back below this number.

>
> Thanks,
> Robert
> ________________________________________
> From: open-ils-general-bounces at list.georgialibraries.org [open-ils-general-bounces at list.georgialibraries.org] On Behalf Of Soulliere, Robert [robert.soulliere at mohawkcollege.ca]
> Sent: July 7, 2010 11:05 PM
> To: Evergreen Discussion Group
> Subject: Re: [OPEN-ILS-GENERAL] Password Reset feature
>
> Thanks Dan,
>
> I made the following changes:
> -installed UUID::Tiny
> -edited the necessary apache files using the 1_6_1_1 examples in the evergreen repository as a guide
> -edited fm_IDL.xml which did not have necessary "aupr" class on my system for some reason.
>
> This is mostly a fresh install. Actually, it started out as an experiment to see what happens to Evergreen when one upgrades from Karmic Koala to Lucid Lynx on a running Evergreen system. My conclusion was that it was necessary to do a fresh install of Evergreen after the upgrade. I removed the openils directory and started from scratch installing openSRF first.
>
> I now have a specific error from the apache error log after a password reset attempt:
>
> [Wed Jul 07 22:10:19 2010] [info] [client 67.204.22.51] Connection to child 16 established (server localhost:443)
> [Wed Jul 07 22:10:19 2010] [info] Seeding PRNG with 656 bytes of entropy
> [Wed Jul 07 22:10:19 2010] [info] Initial (No.1) HTTPS request received for child 16 (server localhost:443)
> [Wed Jul 07 22:11:19 2010] [error] [client 67.204.22.51] Exception: OpenSRF::EX::ERROR 2010-07-07T22:11:19 main -e:0 System ERROR: Exception: OpenSRF::DomainObject::oilsMethodException 2010-07-07T22:11:19 OpenSRF::AppRequest /usr/local/share/perl/5.10.1/OpenSRF/AppSession.pm:1012 <500>   *** Call to [open-ils.actor.patron.password_reset.request] failed for session [1278554902.549123836.7597892563], thread trace [1]:\nException: OpenSRF::EX::Session 2010-07-07T22:11:19 OpenSRF::Application /usr/local/share/perl/5.10.1/OpenSRF/Application.pm:202 Session Error: opensrf at private.localhost/open-ils.cstore_drone_libdog.mohawkcollege.ca_1278554928.561849_8551 IS NOT CONNECTED TO THE NETWORK!!!\n\n\n\n, referer: https://libdog.mohawkcollege.ca/opac/en-CA/skin/default/xml/myopac.xml?l=104&d=-1&at=300
> [Wed Jul 07 22:11:19 2010] [info] [client 67.204.22.51] Connection closed to child 16 with standard shutdown (server localhost:443)
>
> Regards,
> Robert
>
>
>
> This E-mail contains privileged and confidential information intended
> only for the individual or entity named in the message.  If the reader
> of this message is not the intended recipient, or the agent responsible
> to deliver it to the intended recipient, you are hereby notified that
> any review, dissemination, distribution or copying of this communication
> is prohibited.  If this communication was received in error, please
> notify the sender by reply E-mail immediately, and delete and destroy
> the original message.
>
> This E-mail contains privileged and confidential information intended
> only for the individual or entity named in the message.  If the reader
> of this message is not the intended recipient, or the agent responsible
> to deliver it to the intended recipient, you are hereby notified that
> any review, dissemination, distribution or copying of this communication
> is prohibited.  If this communication was received in error, please
> notify the sender by reply E-mail immediately, and delete and destroy
> the original message.

This E-mail contains privileged and confidential information intended
only for the individual or entity named in the message.  If the reader
of this message is not the intended recipient, or the agent responsible
to deliver it to the intended recipient, you are hereby notified that
any review, dissemination, distribution or copying of this communication
is prohibited.  If this communication was received in error, please
notify the sender by reply E-mail immediately, and delete and destroy
the original message.