Real Issue Tracker

We are testing CMS 10.2 but unable to put it into production until the issue of users being unable to change their own password is resolved.

I have created a second instance of CMS and the problem is there too. A solution or workaround would be appreciated.

Thanks.

It could have something to do with the encryption of the passwords. Can you give me some info about the acl_users User Folder that these users are defined in and if it's set up as encryted or not.

Peter,

I'm not at work now but am fairly sure I selected no encryption for passwords. I will check the folder and advise you.

Regards,

Greg.

Peter,

The acl_users folder under the CMS instance was set to have the passwords encrypted.

I unticked "Encrypt user passwords" Updated Existing Passwords, Saved changes and tried changing my password again and had exactly the same result. i.e. the page prompts that the old password is incorrect.

Is there anything else I can do to troubleshoot the problem?

Thanks,

Greg.

What type of user folder is the acl_users? Is it normal "User Folder" or "IssueTracker User Folder"?

The folder is called acl_users (User Folder) and is under the Issue Tracker instance. It was created by the Issue Tracker install. there is another scl_users folder under the Zope control panel.

Peter,

Is there anything we can do to troubleshoot this problem? This is a great product but it's a hassle (and a security risk) for staff not to be able to change their password.

Thanks,

Greg.

Peter,

I'd really like to get the this password change issue resolved. I'm happy to pay for some of your time if necessary. We are now using two different instances of Issue Tracker - one as a Change Management system, to approve system changes and a second as an online Purchase Order system. The customisability of the product makes it very flexible.

They're both working well but I have to get staff to come to my desk if they want to change thier passwords. Both the password change inside IT and the password reminder in the Zope backend fail.

Thanks,

Greg.

Peter,

It's OK thanks. I've finally fixed this problem......

The instructions for the install said that the program needed to be installed in a Zope system that had a mailhost installed. Being new to Zope, I installed a mailhost product and installed the Issue Tracker instance under that.

I've since installed a couple more instnaces of Issue Tracker att eh top of the Zope tree and realised that the password change worked ok in them.

The Zope architecture is so good that I was able to copy and paste all the current issues and users from the "faulty" IT instance to the new one.

Voila! Password changes work fine.

Peter,

It turns out this issue is still occurring. I now have two instances of issue Tracker installed in the correct locations inside Zope but when a user tries to change their password they get "submission incomplete" warning as thought the old password isn't correct.

Any help with this problem would be appreccaiated.

Regards,

Greg.

Fixed now. Please upgrade your SVN version.

Peter,

Many thanks for the fix.

I run a Debian system which uses apt for package management rather than subversion. I've tried setting up svn but it's fairly complex.

Is there another way for me to update Issue Tracker instances to include this fix without using subversion?

Thanks,

Greg.

Peter,

I have managed to get svn working on my Debian server and the command ran ok.

How can I tell if it actually updated the instances of Tracker I have installed? Is there a way of checking the version number from inside Zope?

thanks,

Greg.

Unfortunately there isn't. You can hover over the link in the footer to IssuTrackerProduct.com and see but that only tells you which version was last released so to say, not what SVN revision.