Limiting logins to only browser that requested link through cookies about django-sesame HOT 4 CLOSED

Perhaps in some use cases. However I'm not sure it's a great user experience in general. Having a link that works in browser B but not in browser A is frustrating, especially when A is the default browser.

Currently django-sesame leave the "get link" part entirely up to the user of the library. In my use cases, links are never generated by HTTP requests from a browser, always by command-line scripts, so there's no way to set a cookie at that point.

from django-sesame.

Also, most often, the person who uses the link isn't the same person who generates the link.

from django-sesame.

I just implemented django-sesame and am using it in production. This would be a nice option to help with security a tad. I noticed that Medium doesn't care either.

from django-sesame.

I'm still unsure about what that would mean for django-sesame in practice. If you have a concrete proposal of APIs that django-sesame could implement, let's reopen the discussion.

from django-sesame.