is anyone looking into this?

svet wrote:had to create a new account to start at launch because of that. now my names and our guild are blocked on an inaccessible account.

can i get the reserved stuff transferred onto the new account?
tried to get this sorted pre-launch through irc, but without success.

Hmmm. I looked into it, but I'm not sure where that "stoken" comes from. We're using the Google Identity Toolkit (https://developers.google.com/identity/toolkit/web/) if anyone wants to investigate what could be the issue

hmm well the invalid stoken refers to the Site Secret Key. The only references i could find refer to the captcha plugin not being configured correctly.

Also that stoken is a deprecated feature of reCaptcha API.

We're not using Recaptcha directly, but only indirectly via the Google Identity Toolkit, so I'm not sure what that is doing and how it's getting that stoken :-/

Maybe retracing the configuration of the Google Identity Toolkit can reveal the culprit. Often it's a change in the application environment that came later which is not properly reflected in configuration of such ID tools. 1 changed alias, URI, pathname or similar can screw stuff that up that checks for multiple stuff to be extra save against phishing, XSS, injections, identity theft, etc.. Things I also like to screw up: Uploading config files from the dev plattform to the live service.

TheKrokodil wrote:We're not using Recaptcha directly, but only indirectly via the Google Identity Toolkit, so I'm not sure what that is doing and how it's getting that stoken :-/

Whatever it is you did, the issue seems to have been remediated. I can get in now.

Thanks for looking into this and fixing it.