So I heard that now, when you try to log in, there is sometimes captcha appearing in gameforge client.
I haven't experienced it myself yet, so I have some questions to those who did:
What are the circumstances in order to trigger captcha? Is it random or deterministic?
Is the captcha server-side or client-side? Can you log-in without completing it?
Is it beind sent as answer to post request during auth or something?
Is there way to bypass it?
edit okay, I managed to finally get captcha. Here's how its look like:
You send json post request to spark.gameforge.com/api/v1/auth/thin/sessions with following fields:
identity, password, locale, gfLang, platformGameId, blackbox, gameEnvironmentId, autoGameAccountCreation
blackbox is some kind of long, probably encoded data. didn't figure out how to decode it yet.
after sending such post request, we are welcome by server with 409 response error code.
then there are 2 requests to pixelzirkus, both with 2 cookies: __cfduid and pc_idt, after which we get our images to solve.
After solving the image we are sending response json and request to api/v1/aauth/thin/sessions (this time without gameEnvironmentId) again, which now ends in code 201.
I haven't experienced it myself yet, so I have some questions to those who did:
What are the circumstances in order to trigger captcha? Is it random or deterministic?
Is the captcha server-side or client-side? Can you log-in without completing it?
Is it beind sent as answer to post request during auth or something?
Is there way to bypass it?
edit okay, I managed to finally get captcha. Here's how its look like:
You send json post request to spark.gameforge.com/api/v1/auth/thin/sessions with following fields:
identity, password, locale, gfLang, platformGameId, blackbox, gameEnvironmentId, autoGameAccountCreation
blackbox is some kind of long, probably encoded data. didn't figure out how to decode it yet.
after sending such post request, we are welcome by server with 409 response error code.
then there are 2 requests to pixelzirkus, both with 2 cookies: __cfduid and pc_idt, after which we get our images to solve.
After solving the image we are sending response json and request to api/v1/aauth/thin/sessions (this time without gameEnvironmentId) again, which now ends in code 201.