Apache OpenOffice (AOO) Bugzilla – Issue 7788
Put Password in quotes in notification mails for new users
Last modified: 2021-05-27 19:28:24 UTC
I would like to suggest an improvement of the notification mail for new SC users. > The openoffice.org password for the user 'stx016' is: > E6VGM=/. To make clear that the dot is part of the password it would be good to quote the password (like the user). 'E6VGM=/.'
You have a good point here. Action Plan (AP) 1. Research the issue. 2. Respond back when enough information is available. Step 1 in process.
updating whiteboard
I am able to recreate this issue. I see the following as an example. (The password for your ipssources.com account is: fqqSRVcUTIG Please change it immediately upon logging in.) I am opening a PCN issue for an enhancement request. Eric
I meant openoffice.org on the password example. Eric
After researching this issue with an engineer. We were wondering how the user would know that the qhotes were not part of the password. So do we want to have a line added to say something like. The password is to be utilized literally & contains no punctuation? or something like that? The password should come on a seperate line & should be easily identifiable. Let us know how you would like us to proceed on this issue. Thanks, Eric
Assigning back to OpenOffice. Eric
Hi Eric, As you see in the example, the password MAY contain punctuation. There was a trailing dot, which led to confusion for a user. That's not a story I made up. My suggestion would be to avoid non-alphanumeric characters in password generation. I would write something like The next line contains your password. All 8 characters have to be used - including eventually found punctuation. Thanks, Stefan.
reassigning to support.
Hi Stefan, Yeah, I did not mean to make it sound like a period was made up, I do realize that a period can be in the password. Sorry about that. I am going to go with your suggestion at the end. saying: The next line contains your password. All 8 characters have to be used - including eventually found punctuation. Let me log an internal call & I will update this issue again. I will also update this issue as soon as I get information from engineering. Thanks for your patience here. Eric
Action plan put through request for enhancement Timeframe As soon as I get a response from engineering I will update this issue. Eric
Updated status whiteboard with the pcn number. Eric
This enhancement request is being reviewed by the engineering team. When it is accepted and gets a tentative release schedule CN will update this issue at that time. I am closing as "later".
Reopening the issue for follow-up
This feature request has been considered for a future release . Moving this issue to the resolved later queue .
CollabNet Support is currently reviewing the issues under Resolved-Later. If the issues are fixed currently in any of the present CEE releases, then it will be marked as Resolved-Fixed. There might be a few issues which might not be in our future roadmaps which might be closed as Wontfix unless it does not lie under any custom request.
This has been fixed & verified in the current CEE release 5.2.