<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>Can&#039;t sign in on Chrome 80+ and Firefox 60+ due to cookie &quot;SameSite&quot; restriction</title>
		<link>http://scmapdb.wikidot.com/forum/t-13720675/can-t-sign-in-on-chrome-80-and-firefox-60-due-to-cookie-same</link>
		<description>Posts in the discussion thread &quot;Can&#039;t sign in on Chrome 80+ and Firefox 60+ due to cookie &quot;SameSite&quot; restriction&quot;</description>
				<copyright></copyright>
		<lastBuildDate>Mon, 08 Jun 2026 11:45:39 +0000</lastBuildDate>
		
					<item>
				<guid>http://scmapdb.wikidot.com/forum/t-13720675#post-4804375</guid>
				<title>(no title)</title>
				<link>http://scmapdb.wikidot.com/forum/t-13720675/can-t-sign-in-on-chrome-80-and-firefox-60-due-to-cookie-same#post-4804375</link>
				<description></description>
				<pubDate>Mon, 26 Oct 2020 08:21:13 +0000</pubDate>
				<wikidot:authorName>Anonymous</wikidot:authorName>								<content:encoded>
					<![CDATA[
						 <p>Edge is chrome too. Maybe degrade to IE6.0?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://scmapdb.wikidot.com/forum/t-13720675#post-4772989</guid>
				<title>Can&#039;t sign in on Chrome 80+ and Firefox 60+ due to cookie &quot;SameSite&quot; restriction</title>
				<link>http://scmapdb.wikidot.com/forum/t-13720675/can-t-sign-in-on-chrome-80-and-firefox-60-due-to-cookie-same#post-4772989</link>
				<description></description>
				<pubDate>Sat, 12 Sep 2020 09:10:26 +0000</pubDate>
				<wikidot:authorName>Adambean</wikidot:authorName>				<wikidot:authorUserId>193774</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Chrome since version 80 and Firefox since version 60 introduced a cookie privacy feature, &quot;SameSite&quot;, which in short means that the authentication cookie WikiDot uses does not work cross-domain from &quot;wikidot.com&quot; to &quot;scmapdb.com&quot;.</p> <p>tl;dr: Temporarily use EDGE to work around this problem. (Other browsers may also work, not got Safari to test that.)</p> <p>TOR will also fail as that's based on Firefox.</p> <p>More information here: <a href="http://scp-wiki.wikidot.com/third-party-cookies">http://scp-wiki.wikidot.com/third-party-cookies</a></p> <p>We could work around this issue at a site level by temporarily reversing the redirect from &quot;scmapdb.wikidot.com&quot; to &quot;scmapdb.com&quot;, so that we enforce NOT using our custom domain name, or just temporarily disable the redirect.</p> <p>Otherwise this issue needs to be pressured on WikiDot, as after all this site is a paid service. WikiDot have created an issue for this, but annoyingly left it at medium priority: <a href="https://scuttle.atlassian.net/browse/WDBUGS-9">https://scuttle.atlassian.net/browse/WDBUGS-9</a><br /> This should be a serious priority&#8230; Also annoying that nobody outside WikiDot is allowed to comment on the issue. We can do so here though: <a href="http://community.wikidot.com/forum/t-13660089/i-can-t-login-scpwiki">http://community.wikidot.com/forum/t-13660089/i-can-t-login-scpwiki</a><br /> (I've put my thoughts there given this is a Pro Plus subscription. Not an acceptable time scale!)</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>