Feat/get trusted device cookie #554
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
doubleface
force-pushed
the
master
branch
2 times, most recently
from
f0a89e9
to
ad28199
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here we trying to get the "trustConnect0" cookie from a 303 redirection after OTP loginForm.
We suppose this cookie is the cookie needed to tell the website we're on a trusted device so there is no need to ask for OTP everytime, but for now we cannot find a way to get it.
I let this PR in draft so we can use what's already done (such as stoping on the 303 response where the cookie is supposed to be set) later, when we'll come back on this.
For now the konnector is functionnal, it's just asking for the OTP every connections.