Apache OpenOffice (AOO) Bugzilla – Issue 22913
Outstanding password tickets
Last modified: 2006-02-14 18:53:55 UTC
After migration domain admins have an entry in the Pending actions section * Outstanding password tickets (2,207) Why are they generated and how they be handled?
opened internal issue 24384 to get an answer
It is a historical list of anyone who has requested a password ticket and never used it. This is a static list that simply grows over time. No action is required.
The header for the section on My Start Page says "Pending Actions" :-) First, the users currently listed never requested password tickets. They have been migrated. Why do they have outstanding password changes? I guess the tickets are issued because the user's passwords don't follow the password security settings. Second, there should be a way for administrators to get rid of the "pending action". A usability problem is that there is no way to select all users (of the shown page) for reissuing their ticket. Do you expect us (the domain admins) to reissue 2,200 tickets one by one? I could imagine to have a reissue counter for each user. Then the domain admin would reissue the ticket for users 3 times and then delete the account. If - as last ressort - you really think there is no action needed then we should have a way to show/hide this entry from the "Pending Actions".
This is a list of all unused password ticket requests from the beginning point of time on the OOo production site. These users may have requested a password ticket quite some time ago. This is not a new list that was created as a byproduct of migration. There is no way to clear these pending actions. The user must use their password ticket for the event to be removed. The system will keep a track of this indefinately. Show/Hide/Delete of these pending actions is an enhancement request.
I don't understand what "requesting a password ticket" for 1.1.3 (and earlier versions) means. There was no password ticket system. Could you explain what the users did so that they appear in the list. The admin UI remains unusable for this number of tickets. I would like to reissue the tickets. How about a "reissue all" button?
When the user presses the "new password" button on the login screen a password ticket (e-mail) is sent to them. If they do not follow through with the instructions (utilize the ticket) it sits as a pending action within SourceCast. The user's failure to utilize the ticket could be for a variety of reasons - like contacting the domain admins to personally reset their password again. You have never seen this queue before. We started showing it in version 2.x even though it has been there all along. A "reissue all" button is an enhancement request to be filed with support once the upgrade is complete.
So, may I ask again what you recommend to do with ~2200 outstanding tickets?
Well, there is really nothing to do if the user did not utilize the e- mail sent to them. Some of them originated in 2001, if not earlier. One option is to open a post upgrade support issue to have CN ops delete them if you wish.
We had 110,000 registered users in Oct 2003. In Jan 2004 we are at 125,000. We had 2,200 outstanding password tickets in Oct 2003. In Jan 2004 we are at 5,000. As recommended by Steve I filed issue 24859 for the task to reset old tickets. Additionally I requested an enhancement to allow the handling of registered but unsued accounts (with outstanding password tickets) in issue 24861.
Let's close old, resolved isssues...