Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: Authenticated user URL can't be found. The page format might have changed. #10

Open
jlangeveld opened this issue Jun 7, 2019 · 15 comments

Comments

@jlangeveld
Copy link

After solving the Captcha during login and copy-pasting the resulting response, the script seems to hit an updated page

@ghost
Copy link

ghost commented Jul 19, 2019

I can confirm this bug.
@TnS-hun

@jmvermeulen
Copy link

I can confirm is DOES work. No issue logging in and authenticate.

@ghost
Copy link

ghost commented Sep 27, 2019

I think I have found the problem (but I am unable to solve it) - the script does not work if you are using Rakuten ID (楽天ID).

Rakuten ID is not the same as the "Rakuten Kobo" login method.
If you created your account on https://www.kobo.com, then this script should work (since the "Rakuten Kobo" login method is used).
If you use https://books.rakuten.co.jp/e-book/ (which sells e-books written in Japanese), then you have a Rakuten ID.

@jlangeveld
Copy link
Author

Yeah, that would be my problem too.
I have a bol.com account - a reseller in the Netherlands.

@ghost
Copy link

ghost commented Sep 28, 2019

By the way, while changing from Affiliate = "Kobo" to Affiliate = "Rakuten" can avoid the Authenticated user URL can't be found error (i.e. a kobo:https://UserAuthenticated response is received), it gives requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: https://storeapi.kobo.com/v1/auth/device instead.

Maybe there are some more parameters that have to be changed if another login provider is used?

@jmvermeulen
Copy link

I think this can be fixed easily.
Create a new Kobo account (without a external login provider). In the user profile page you can link it to another account. Choose your existing with books.

Now you can authenticate with Kobo credentials on you existing account. I tried it, it works :-)

@mintgriff
Copy link

I'm having a similar CAPTCHA problem.

after i paste it into terminal i get
ERROR: Can't find the workflow ID in the login form. The page format might have changed.

I originally signed up and used Google log-in.
I tried creating a new account without google log-in, and then linked it to my existing account.
Tested logging in through the site with new login, it works, and my purchase history is there.
However, still getting the error in terminal after pasting the code after solving the captcha.
Any ideas of what i might be doing wrong?

Captcha response: 03AOLTBLSMv1TQTypniy0SNxyQTND0k8URzOo1hgI7koanVaIwwScECELA5zDcPsOQD9l5R-Y-Q9DIS4pu8BpNFtkrPAJ_So99jqajTXUn8Pwe_ZTTaDoKGhfrsSkNQGYdk0zyN1D5SsboyCNE18QhLFbTHFE2qy6DSushUt7AYdZpaoWHv6w5yUZznrqBe_6a017-G5d9OSj-EKJpb2T15aVw2PAneajzGzZ2LZ15vCINMub4ElYzsed6-zofwMVAKiXh981GPRX-ulV0hkJhDxoRErV3rPcfiQPG3vkk13iHbP_0bUawxVc90mDG1cAwhywLhvXhoZWIh5-H91SZoRpFqSE-pnZIOV2T-QqgbLqXm43aUaE3xojjE3aqmVtpnNTYbhIbRZ5u56JONEaeCDVKC-aVRPPTnK-pLku9EU6CQLN0oP7jjsFJjL1cpfFlPMoDxfx9YJezD0h7WsIHevM8g8oVkhXWREHY6fJb2WS7g3BZZy9T2NZ_GsHop75-A6cduQKbmm5m3osw88HeME1FBXzUMmeibGeXkr7IPiAc_QjbuQERJyDMilRZYU6smFKtrOQTCDTv

ERROR: Can't find the workflow ID in the login form. The page format might have changed.

@shelaffs
Copy link

Can confirm I received this error as well. I use a Rakuten (kobo.com) login and after entering the code from the captcha, I cannot move forward.

@subdavis
Copy link

I had this issue as well.

I took a look at the page it's trying to parse the workflow ID out of, and happened to notice it's always the same string, but it's no longer autopopulated in the form this script wants it in.

I modified Kobo.py:

		# match = re.search( r""" name="LogInModel.WorkflowId" type="hidden" value="([^"]+)" />""", htmlResponse )
		# if match is None:
		# 	raise KoboException( "Can't find the workflow ID in the login form. The page format might have changed." )
		# workflowId = html.unescape( match.group( 1 ) )
		workflowId = '67af1c98-1a87-4144-8a1f-bae9379477f1'

And after this, auth succeeded.

I'll try to come up with a more solid workaround soon.

@subdavis
Copy link

subdavis commented Jan 12, 2020

For anyone still experiencing this issue, you can use my fixed fork @ https://github.com/subdavis/kobo-book-downloader until the change is merged to master 👍

@jlangeveld
Copy link
Author

I think this can be fixed easily.
Create a new Kobo account (without a external login provider). In the user profile page you can link it to another account. Choose your existing with books.

Now you can authenticate with Kobo credentials on you existing account. I tried it, it works :-)

I can confirm that this workaround works, thanks

@subdavis
Copy link

@jlangeveld please repoen this issue. It's still a bug that needs to be fixed, and the maintainer needs to merge my pull request.

Glad this fixed it for you.

@jlangeveld
Copy link
Author

Reopened by request

@jlangeveld jlangeveld reopened this Jan 13, 2020
@subdavis
Copy link

subdavis commented Apr 1, 2020

This repository has been abandoned. I have forked the project at https://github.com/subdavis/kobo-book-downloader - please give that project a try and open an issue there if you have trouble.

It adds some new features:

  • multi-user support; fetch books for multiple accounts.
  • web interface; adds new browser gui (with flask)
  • docker image
  • pypi package

Please don't reply to this issue, open an issue on my fork instead

@jlangeveld
Copy link
Author

@subdavis I've got your fork running, great work!
Your fork's repo doesn't have Issues activated...

Also, the workaround that was described above is still needed (and it still works great), so perhaps you could describe it in the Readme...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants