<?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[Using FusionAuth without migrating data into it]]></title><description><![CDATA[<p dir="auto">My company's probably going to implement SSO for our app next year as it's a fairly common enterprise requirement for vendors. We want to minimize the amount of work needed to get this up and working.</p>
<p dir="auto">From what I can tell, most platforms need some kind of migration into their own user store. Does FusionAuth work in a purely federated way?</p>
]]></description><link>https://fusionauth.io/community/forum/topic/560/using-fusionauth-without-migrating-data-into-it</link><generator>RSS for Node</generator><lastBuildDate>Tue, 09 Jun 2026 08:52:15 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/560.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 16 Nov 2020 16:27:02 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Using FusionAuth without migrating data into it on Mon, 16 Nov 2020 16:29:29 GMT]]></title><description><![CDATA[<p dir="auto">Yes, you can have FusionAuth simply federate identity and not hold anything permanent in its own datastore. SSO should work in that case.</p>
<p dir="auto">Two options:</p>
<ul>
<li>If your existing user store can speak SAML or OIDC, you should be able to use an identity provider <a href="https://fusionauth.io/docs/v1/tech/identity-providers/" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/identity-providers/</a> You would need to modify the theme and you'd probably want to use a hint.</li>
<li>If your existing user store can speak LDAP or a JSON API, you can use connectors without migrating (this is a feature for which you must buy at least a developer license, starting at 125/month, more here: <a href="https://fusionauth.io/pricing/" rel="nofollow ugc">https://fusionauth.io/pricing/</a> ). Here's more on connectors: <a href="https://fusionauth.io/docs/v1/tech/connectors/" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/connectors/</a></li>
</ul>
<p dir="auto">In both these cases, FusionAuth communicates with your userstore through some kind of facade, not directly with the database. Such direct database access isn't supported.</p>
<p dir="auto">I'm not sure how this will work for all aspects of FusionAuth (password expiration, passwordless, etc) but for the main login flows it should work great.</p>
]]></description><link>https://fusionauth.io/community/forum/post/1699</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/1699</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Mon, 16 Nov 2020 16:29:29 GMT</pubDate></item></channel></rss>