#28119: Test client cookies do not take into account server hostnames/domains
-------------------------------------+-------------------------------------
Reporter: Ali Kaafarani | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: 1.11
Severity: Normal | Resolution:
Keywords: test, client, | Triage Stage:
cookie, domain | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Ali Kaafarani):
The use case in my project is to test single sign-on functionality. In one
case, we need to log the user in on one site but not the other. Then, when
the user visits the second site, they should be redirected and
automatically authenticated. However, in the test framework, the session
cookie will be sent to both sites after authenticating on only one,
because the hostnames aren't taken into consideration. So the SSO features
cannot be properly tested. I agree that this is probably not a very common
use case, and does add some complexity to the simple client.
I would love to put this together in a Client subclass as a proof of
concept. I will try to do so when I get the free time (although that may
take a while).
--
Ticket URL: <https://code.djangoproject.com/ticket/28119#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.397523eebca263601f3ee9de7d4d533b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
