Hey all,
Just a quick update. I will hopefully be making an official post soon with more details (and apologies!) later in the day.
If you're using a "loophole" to login to the community you are going to sometimes (more than likely) see someone else's SAN + Name. We wanted to stop this from happening but looks like it is not working out because of the "loophole". I know many of you are upset because we did not do enough testing, checking, high-level coding, etc, etc. Unfortunately I only get to be the solution in this case but we'll talk about that more later.
We've developed a way to fix this issue and will be doing another round of testing of it today, then we will roll it out to those we have seen post about it so far. If we need more info, we'll reply to one of your posts or comments to get your attention.
In regards to the certificate issue on the old URL - that should be addressed on Monday. New users to the community will be directed to the correct URL when trying to access it via the Support Center. Those using bookmarks or manually typing in the old URL will be shown the certificate error, at least until Monday. We'll post another update about that come Monday.
Regarding the e-mail verification and not receiving them/getting errors... Seems people tried over and over to get logged in, prompting a flood of these e-mail verification e-mails to basically storm our servers. Many of them did not make it through because of this, but after a lengthy conference yesterday, we managed to get both the emails flowing and the verification letters working. In this case, sometimes receiving more than one verification e-mail threw an error that you couldn't be verified.
Just wanted to say we know this is super frustrating and came without warning. We too were in the same situation with verification emails and logging in that you all were. Please know we have learned a very valuable lesson this week and are planning out better strategies for the future.
Thanks
Amanda
P.S. Yes - we're going to work on the new categories layout, but want to get these game-breaking login issues fixed first.
