Added authentication using browser cookie to bypass CHALLENGE #471
Conversation
|
+1 for this PR. I was getting CHALLENGE failures, installed this version with I also only needed to copy the cookies for the first time. All succeeding requests (so far) haven't required entering the cookies again. |
| self._do_authentication_request(username, password) | ||
| except ChallengeException: | ||
| self.logger.warning("ChallengeException encountered during authentication.") | ||
| jsessionid = input("Enter your JSESSIONID cookie from the browser: ") |
There was a problem hiding this comment.
@ArujAnand love this idea! My only concern is that this might break some functionality for folks who are running the library on a server somewhere (without a human sitting at the keyboard).
What do you think about adding a parameter to __init__ - something like challenge_prompt_enabled (default to false) - that allows users to turn this behavior on and off?
JSESSIONID, li_at cookies can be taken from the browser and be added for authentication to bypass CHALLENGE