You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am seeing cross-site-request-forgery warnings raised by scope when trying to login within the same browser I am logged into Archivematica both systems running in their own docker environments locally.
At the very least, this seems to be due to Django cookie naming.
So within settings.py I can set CSRF_COOKIE_NAME = "COLIN" to quieten that, and then I can happily log into both without the warning appearing.
Equally, I can create a similar setting inside Archivematica's Dashboard settings: here.
That gets me further down the road.
The second issue is that there still seems to be some interference between the two applications where logging into one logs you out of the other. This is less inconvenient. My focus is elsewhere today so I might come back to this, but it means I haven't been able to debug that further.
Tested in both Firefox and Chrome.
The text was updated successfully, but these errors were encountered:
I am seeing cross-site-request-forgery warnings raised by scope when trying to login within the same browser I am logged into Archivematica both systems running in their own docker environments locally.
At the very least, this seems to be due to Django cookie naming.
So within settings.py I can set
CSRF_COOKIE_NAME = "COLIN"
to quieten that, and then I can happily log into both without the warning appearing.Equally, I can create a similar setting inside Archivematica's Dashboard settings: here.
That gets me further down the road.
The second issue is that there still seems to be some interference between the two applications where logging into one logs you out of the other. This is less inconvenient. My focus is elsewhere today so I might come back to this, but it means I haven't been able to debug that further.
Tested in both Firefox and Chrome.
The text was updated successfully, but these errors were encountered: