<?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[Getting error with OIDC identity provider]]></title><description><![CDATA[<p dir="auto">When I am trying to set up a <a href="https://fusionauth.io/docs/v1/tech/identity-providers/openid-connect/" rel="nofollow ugc">OIDC identity provider</a>, I am seeing an error after I login: <code>invalid_origin</code>.</p>
<p dir="auto">When I look at the event log I see:</p>
<pre><code>Request to the [https://REDACTED/userinfo] endpoint failed. Status code [200].Exception encountered.com.inversoft.rest.JSONException : Message: Failed to parse the HTTP response as JSON. Actual HTTP response body:
eyJra...
</code></pre>
<p dir="auto">If I decoded the JWT in the response body, I get back a valid userinfo response.</p>
<p dir="auto">How can I handle this?</p>
]]></description><link>https://fusionauth.io/community/forum/topic/834/getting-error-with-oidc-identity-provider</link><generator>RSS for Node</generator><lastBuildDate>Sun, 14 Jun 2026 14:10:55 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/834.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 23 Feb 2021 16:15:44 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Getting error with OIDC identity provider on Tue, 23 Feb 2021 16:20:08 GMT]]></title><description><![CDATA[<p dir="auto">That is an encoded (signed) JWT being sent in response to the user info request that the FusionAuth OIDC identity provider is making.</p>
<p dir="auto">This is technically allowed in the <a href="https://openid.net/specs/openid-connect-core-1_0.html#UserInfoResponse" rel="nofollow ugc">OIDC spec</a>, but we do not currently support this response type.</p>
<p dir="auto">Per spec, the endpoint should support a JSON response which is the default unless the client requests a signed or encrypted response body.</p>
<p dir="auto">I would look at how your client is registered and see if it is asking for a JWT userinfo response at that time, and change it to be a normal JSON response. You could also <a href="https://github.com/fusionauth/fusionauth-issues/issues" rel="nofollow ugc">file an issue</a> detailing your needs for FusionAuth to support this user info response type.</p>
<p dir="auto">If that isn't an option, you could also look at using a SAML Identity Provider if the remote identity source supports that.</p>
]]></description><link>https://fusionauth.io/community/forum/post/2466</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/2466</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Tue, 23 Feb 2021 16:20:08 GMT</pubDate></item></channel></rss>