Closed Wissperwind closed 1 year ago
I've been using this package for a while and started having this issue when I tried upgrading Django from 3.2 to 4.0. Since my project is already dependent on this package, I can't upgrade django until this bug is fixed .
ok, so this is an django issue or an issue of this project?
I did some digging into this. Django 4.0 added a security feature that breaks how this page was working. This change causes these two lines to error since window.opener
is null.
OK, and now?
H Guys, I have same issue as well. Is anyone working on it as i am using Django 4.1.3. Any suggestions?
The solution in in the documentation link above. Set
# settings.py
SECURE_CROSS_ORIGIN_OPENER_POLICY = "none"
https://docs.djangoproject.com/en/4.1/ref/middleware/#cross-origin-opener-policy https://docs.djangoproject.com/en/4.1/ref/settings/#std-setting-SECURE_CROSS_ORIGIN_OPENER_POLICY
Thank you. That solved my problem!!!
Hi,
I just set up microsoft login. I try to login into django admin. The user was created by the plugin and I already gave him staff and admin permission by using a superuser. But the moment the microsoft login is completed, the window shows:
But:
If close manually and afterwards refresh manually the user is logged in. But that can't be the way a user should log in.