You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[email protected] (this user reported the same: [email protected] ) : it’s working today! I accessed with the temporary password ‘ChangeM3!’ and was able to change the password in Account Security successfully.
In GCollab, our team has been using the pilot GCmessage tool – which we understand will cease to work on August 12.
When I tried to access GCmessage, I got this screen – type your new password:
So I just typed the same new password I changed earlier and was able to access the GCmessage.
I then logged out, cleared cache, and logged in GCollab again, with no problem using new password. And again got the same screen when clicked GCmessage. So I typed random text (not new password) but system allowed me to access GCmessage regardless (seems like another bug). Not sure if you will correct this bug since GCmessage seems to be ending (which is too bad, we actually used it quite heavily and found it useful!)
The text was updated successfully, but these errors were encountered:
This issues appears to be caused by using capital letters in a user's email address.
Fix: Force all email forms entries to lowercase. Write script to modify all existing user accounts to lower case emails.
[email protected] (this user reported the same: [email protected] ) : it’s working today! I accessed with the temporary password ‘ChangeM3!’ and was able to change the password in Account Security successfully.
In GCollab, our team has been using the pilot GCmessage tool – which we understand will cease to work on August 12.
When I tried to access GCmessage, I got this screen – type your new password:
So I just typed the same new password I changed earlier and was able to access the GCmessage.
I then logged out, cleared cache, and logged in GCollab again, with no problem using new password. And again got the same screen when clicked GCmessage. So I typed random text (not new password) but system allowed me to access GCmessage regardless (seems like another bug). Not sure if you will correct this bug since GCmessage seems to be ending (which is too bad, we actually used it quite heavily and found it useful!)
The text was updated successfully, but these errors were encountered: