<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Upgrading from 1.46.0 to 1.47.1 CSRF token issue with IdP]]></title><description><![CDATA[<p dir="auto"><strong>What i am trying to do</strong><br />
I am trying to step by step update a old fusionauth instance. I have a fully working fusionauth 1.46.0 that i am now trying to get working for 1.47.1.</p>
<p dir="auto">I have deployed 1.47.1 where previously 1.46.0 was deployed. After the upgrade everything seems to work fine except for our identity provider login (even when trying to login into the fusionauth admin panel itself with identity provider login). I receive the message "The request origin could not be verified. Unable to complete this login request."  I can still login normally using the login form.</p>
<p dir="auto"><strong>What i expected to see</strong><br />
I expected to be logged in after using the identity provider login button.</p>
<p dir="auto"><strong>What i have tried already</strong><br />
After reading patch notes i noticed changes regarding origin URL changes and CSRF changes that may break custom themes. Therefore i turned off our custom theme and set it back to the default. I also cleared our origin URLs in the application settings to no avail.</p>
<p dir="auto"><strong>Infrastructure information</strong><br />
Our fusionauth instance is run in AWS Elastic Beanstalk with a RDS PostgreSQL database. Our fusionauth instance consists out of 2 nodes.</p>
<p dir="auto">The issuer for our identity provider is "<a href="https://login.microsoftonline.com" rel="nofollow ugc">https://login.microsoftonline.com</a>".<br />
The scope is set to "openid profile email "<a href="https://graph.microsoft.com/user.read" rel="nofollow ugc">https://graph.microsoft.com/user.read</a>".<br />
Client authentication is "HTTP basic authentication (client_secret_basic)". It is Enabled for all our applications.</p>
<p dir="auto">The identity provider issuer receives the identity provider calls from fusionauth and returns HTTP response code 200.</p>
<p dir="auto">After trying to login nothing new is shown in the log of node 1 or 2.</p>
<p dir="auto">Thanks in advance for any support.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2682/upgrading-from-1-46-0-to-1-47-1-csrf-token-issue-with-idp</link><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Jul 2026 03:16:11 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/2682.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 15 May 2024 08:34:45 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Upgrading from 1.46.0 to 1.47.1 CSRF token issue with IdP on Tue, 10 Sep 2024 02:19:15 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/1985">@egli</a> said in <a href="/community/forum/post/7341">Upgrading from 1.46.0 to 1.47.1 CSRF token issue with IdP</a>:</p>
<blockquote>
<p dir="auto">Similar issue and was able to resolve it by following changes mentioned here:<br />
<a href="https://fusionauth.io/docs/release-notes/#version-1-47-0" rel="nofollow ugc">https://fusionauth.io/docs/release-notes/#version-1-47-0</a> <a href="https://slice-master.io" rel="nofollow ugc">slice master</a></p>
</blockquote>
<p dir="auto">Can you explain in more detail?</p>
]]></description><link>https://fusionauth.io/community/forum/post/7509</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/7509</guid><dc:creator><![CDATA[eachhabitual]]></dc:creator><pubDate>Tue, 10 Sep 2024 02:19:15 GMT</pubDate></item><item><title><![CDATA[Reply to Upgrading from 1.46.0 to 1.47.1 CSRF token issue with IdP on Fri, 14 Jun 2024 15:03:57 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3016">@tvdlooy</a> were you able to resolve this?</p>
]]></description><link>https://fusionauth.io/community/forum/post/7343</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/7343</guid><dc:creator><![CDATA[[[global:former-user]]]]></dc:creator><pubDate>Fri, 14 Jun 2024 15:03:57 GMT</pubDate></item><item><title><![CDATA[Reply to Upgrading from 1.46.0 to 1.47.1 CSRF token issue with IdP on Fri, 14 Jun 2024 09:00:37 GMT]]></title><description><![CDATA[<p dir="auto">Similar issue and was able to resolve it by following changes mentioned here:<br />
<a href="https://fusionauth.io/docs/release-notes/#version-1-47-0" rel="nofollow ugc">https://fusionauth.io/docs/release-notes/#version-1-47-0</a></p>
]]></description><link>https://fusionauth.io/community/forum/post/7341</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/7341</guid><dc:creator><![CDATA[egli]]></dc:creator><pubDate>Fri, 14 Jun 2024 09:00:37 GMT</pubDate></item><item><title><![CDATA[Reply to Upgrading from 1.46.0 to 1.47.1 CSRF token issue with IdP on Tue, 28 May 2024 14:45:13 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/2507">@mark-robustelli</a> No this is one of the main issues we have with trying to troubleshoot this issue, because nothing new happens in the fusionauth-app.log after this error is triggered.</p>
]]></description><link>https://fusionauth.io/community/forum/post/7312</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/7312</guid><dc:creator><![CDATA[tvdlooy]]></dc:creator><pubDate>Tue, 28 May 2024 14:45:13 GMT</pubDate></item><item><title><![CDATA[Reply to Upgrading from 1.46.0 to 1.47.1 CSRF token issue with IdP on Tue, 28 May 2024 14:17:05 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3016">@tvdlooy</a> Is there anything in the logs that refers to this issue?</p>
]]></description><link>https://fusionauth.io/community/forum/post/7300</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/7300</guid><dc:creator><![CDATA[mark.robustelli]]></dc:creator><pubDate>Tue, 28 May 2024 14:17:05 GMT</pubDate></item><item><title><![CDATA[Reply to Upgrading from 1.46.0 to 1.47.1 CSRF token issue with IdP on Wed, 22 May 2024 08:52:22 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/2507">@mark-robustelli</a> I have now tried removing it and adding it back again. I also tried to make a completely new instance with the same settings and i keep receiving the error, "The request origin could not be verified. Unable to complete this login request. ".</p>
]]></description><link>https://fusionauth.io/community/forum/post/7296</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/7296</guid><dc:creator><![CDATA[tvdlooy]]></dc:creator><pubDate>Wed, 22 May 2024 08:52:22 GMT</pubDate></item><item><title><![CDATA[Reply to Upgrading from 1.46.0 to 1.47.1 CSRF token issue with IdP on Fri, 17 May 2024 21:52:23 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3016">@tvdlooy</a> Could you try to remove the identity provider login and then add it back? You should not need to, but if that works it could let us know that something else got messed up.</p>
]]></description><link>https://fusionauth.io/community/forum/post/7276</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/7276</guid><dc:creator><![CDATA[mark.robustelli]]></dc:creator><pubDate>Fri, 17 May 2024 21:52:23 GMT</pubDate></item></channel></rss>