<?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[Topics tagged with connectors]]></title><description><![CDATA[A list of topics that have been tagged with connectors]]></description><link>https://fusionauth.io/community/forum/tags/connectors</link><generator>RSS for Node</generator><lastBuildDate>Tue, 21 Apr 2026 13:20:11 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/connectors.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Connector not persisting claim]]></title><description><![CDATA[<p dir="auto">There is no way to get back information from FA when it calls your connector endpoint.  What I ended up doing was creating separate applications for each portal in our app.   WHen FA calls my connector, now I can look at the incoming applicationid and know which portal this user belongs too and that solved my issue.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2642/connector-not-persisting-claim</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2642/connector-not-persisting-claim</guid><dc:creator><![CDATA[helzgate]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Connector service docs say it needs only user.id, but fails it not given email too]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/20">@dan</a> Oh I see. The error in the response says:</p>
<p dir="auto">"because it was missing a unique id in the [<a href="http://user.id" rel="nofollow ugc">user.id</a>] or enough information to store in FusionAuth (i.e. an email or username)"</p>
<p dir="auto">In other words, "either Id or email" is missing from your request. Which makes boolean sense when thinking about it carefully.</p>
<p dir="auto">But when first reading it, I though it meant "you need either Id or email", which is very different. I supplied one of those. I though that was what the "or" meant.</p>
<p dir="auto">This error could be better as:</p>
<p dir="auto">"because it was missing a unique id in the [<a href="http://user.id" rel="nofollow ugc">user.id</a>] or enough information to store in FusionAuth (i.e. an email or username). Both are necessary"</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2641/connector-service-docs-say-it-needs-only-user-id-but-fails-it-not-given-email-too</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2641/connector-service-docs-say-it-needs-only-user-id-but-fails-it-not-given-email-too</guid><dc:creator><![CDATA[fusionauth.qhj5e]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Facing duplicate key errors on high load]]></title><description><![CDATA[<p dir="auto">Internal Note: tracking via <a href="https://github.com/FusionAuth/fusionauth-issues/issues/1231" rel="nofollow ugc">https://github.com/FusionAuth/fusionauth-issues/issues/1231</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/1005/facing-duplicate-key-errors-on-high-load</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1005/facing-duplicate-key-errors-on-high-load</guid><dc:creator><![CDATA[joshua]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Can we increase timeout of the login request?]]></title><description><![CDATA[<p dir="auto">You can increase the timeout of the login request to a connector. If you sign in to the admin UI and navigate to "Settings" and then "Connectors", you can modify either of these settings:</p>

"Connect timeout"
"Read timeout"

<p dir="auto">The default value for these is 2 seconds.</p>
<p dir="auto">There is more documentation on this topic here: <a href="https://fusionauth.io/docs/v1/tech/connectors/generic-connector/" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/connectors/generic-connector/</a></p>
<p dir="auto">You can also change them via the API, if that's more in line with your current workflow. That's documented here: <a href="https://fusionauth.io/docs/v1/tech/apis/connectors/generic/#update-the-generic-connector" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/apis/connectors/generic/#update-the-generic-connector</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/643/can-we-increase-timeout-of-the-login-request</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/643/can-we-increase-timeout-of-the-login-request</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[What can I use connectors for?]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/645">@joshua</a> That actually helps very much, thanks!</p>
]]></description><link>https://fusionauth.io/community/forum/topic/455/what-can-i-use-connectors-for</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/455/what-can-i-use-connectors-for</guid><dc:creator><![CDATA[elliotdickison]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>