As there is already a thread open on this subject with an official response, we've closed this thread to consolidate reports on this log in issue and make it easier on the team to review. Please refer to the thread here for further updates on the issue.