<?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 integration]]></title><description><![CDATA[A list of topics that have been tagged with integration]]></description><link>https://fusionauth.io/community/forum/tags/integration</link><generator>RSS for Node</generator><lastBuildDate>Fri, 10 Jul 2026 17:40:56 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/integration.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[How to Resolve &#x27;Your Account Has Expired&#x27; Errors in FusionAuth]]></title><description><![CDATA[<p dir="auto">To update or extend a user’s account expiry date, you can use the FusionAuth User API to modify the <strong>expiry</strong> field. You can either set a new expiration date or set the field to <strong>null</strong> to remove the expiry entirely.</p>
<p dir="auto">Here’s an example of a <strong>PATCH</strong> request to update this field:</p>
curl --request PATCH \
  --url https://local.fusionauth.io/api/user/42661043-9ab8-4bb8-8778-85217aa05086 \
  --header 'Authorization: TulwCDDOmOtvXAVTsRUI4LfSWlF-Bd78uTnQhgviMQG9a1a3Qn7emwBn' \
  --header 'Content-Type: application/json' \
  --header 'X-FusionAuth-TenantId: 30665132-6767-6665-3132-323466613934' \
  --data '{
    "user": {
      "expiry": null
    }
  }'

<p dir="auto">Explanation:<br />
Replace the URL, user ID, and tenant ID with your instance's values.<br />
Setting <strong>"expiry": null</strong> removes the expiration date and reactivates the user account.<br />
This should resolve the issue and allow the user to log in again.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2972/how-to-resolve-your-account-has-expired-errors-in-fusionauth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2972/how-to-resolve-your-account-has-expired-errors-in-fusionauth</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Managing User IDs in FusionAuth: Options for Addressing Incorrect Assignments]]></title><description><![CDATA[<p dir="auto">Unfortunately, FusionAuth does not support changing a user’s ID after the user has been created.</p>
<p dir="auto">However, when creating users via API, you can specify a custom user ID at the time of creation. This allows you to control user IDs during the initial setup.</p>
<p dir="auto"><strong>API Reference</strong>:</p>

<a href="https://fusionauth.io/docs/apis/users#create-a-user" rel="nofollow ugc">Create a User API</a>

<p dir="auto">Since the IDs are already assigned, your best option might be to adjust your integration logic or recreate the users with the desired IDs.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2964/managing-user-ids-in-fusionauth-options-for-addressing-incorrect-assignments</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2964/managing-user-ids-in-fusionauth-options-for-addressing-incorrect-assignments</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Bulk Registering Existing Users to New Applications in FusionAuth]]></title><description><![CDATA[
<strong>Bulk Registration of Existing Users</strong>:<br />
FusionAuth does not currently provide a bulk endpoint for creating user registrations. However, you can achieve this by using the Create User Registration API to programmatically register users to <strong>app2</strong>. This requires iterating through the list of existing users and making an API call for each user to add the new registration.
<strong>Best Practices for Future Scenarios</strong>:<br />
To avoid manual one-time activities like this in the future, consider the following approaches:

<strong>Enable Self-Service Registration</strong>:<br />
If you are using FusionAuth's hosted login pages for user sign-ins, you can enable self-service registration for <strong>app2</strong>. With this feature, a user will automatically have a registration created for <strong>app2</strong> when they attempt to log in for the first time.
<strong>Programmatic Registration</strong>:<br />
Implement a workflow in your onboarding process that ensures users are automatically registered to all relevant applications when they are created or updated in your system.
<strong>Custom Scripts for Batch Processing</strong>:<br />
Write a script to fetch all existing users and register them to any new applications as needed. This can be reused whenever new applications are added to your system.



<p dir="auto"><strong>References</strong>:</p>

<a href="https://fusionauth.io/docs/apis/registrations#create-a-user-registration-for-an-existing-user" rel="nofollow ugc">Create User Registration API</a>
<a href="https://fusionauth.io/docs/lifecycle/register-users/basic-registration-forms#self-service-registration-and-registrations" rel="nofollow ugc">Self-Service Registration</a>

<p dir="auto">These steps should help streamline your workflow and reduce manual intervention for future scenarios.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2950/bulk-registering-existing-users-to-new-applications-in-fusionauth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2950/bulk-registering-existing-users-to-new-applications-in-fusionauth</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Bulk Registering Existing Users to New Applications in FusionAuth]]></title><description><![CDATA[
<strong>Bulk Registration of Existing Users</strong>:<br />
FusionAuth does not currently provide a bulk endpoint for creating user registrations. However, you can achieve this by using the Create User Registration API to programmatically register users to <strong>app2</strong>. This requires iterating through the list of existing users and making an API call for each user to add the new registration.
<strong>Best Practices for Future Scenarios</strong>:<br />
To avoid manual one-time activities like this in the future, consider the following approaches:

<strong>Enable Self-Service Registration</strong>:<br />
If you are using FusionAuth's hosted login pages for user sign-ins, you can enable self-service registration for <strong>app2</strong>. With this feature, a user will automatically have a registration created for <strong>app2</strong> when they attempt to log in for the first time.
<strong>Programmatic Registration</strong>:<br />
Implement a workflow in your onboarding process that ensures users are automatically registered to all relevant applications when they are created or updated in your system.
<strong>Custom Scripts for Batch Processing</strong>:<br />
Write a script to fetch all existing users and register them to any new applications as needed. This can be reused whenever new applications are added to your system.



<p dir="auto"><strong>References</strong>:</p>

<a href="https://fusionauth.io/docs/apis/registrations#create-a-user-registration-for-an-existing-user" rel="nofollow ugc">Create User Registration API</a>
<a href="https://fusionauth.io/docs/lifecycle/register-users/basic-registration-forms#self-service-registration-and-registrations" rel="nofollow ugc">Self-Service Registration</a>

<p dir="auto">These steps should help streamline your workflow and reduce manual intervention for future scenarios.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2851/bulk-registering-existing-users-to-new-applications-in-fusionauth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2851/bulk-registering-existing-users-to-new-applications-in-fusionauth</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Managing User IDs in FusionAuth: Options for Addressing Incorrect Assignments]]></title><description><![CDATA[<p dir="auto">Unfortunately, FusionAuth does not support changing a user’s ID after the user has been created.</p>
<p dir="auto">However, when creating users via API, you can specify a custom user ID at the time of creation. This allows you to control user IDs during the initial setup.</p>
<p dir="auto"><strong>API Reference</strong>:</p>

<a href="https://fusionauth.io/docs/apis/users#create-a-user" rel="nofollow ugc">Create a User API</a>

<p dir="auto">Since the IDs are already assigned, your best option might be to adjust your integration logic or recreate the users with the desired IDs.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2830/managing-user-ids-in-fusionauth-options-for-addressing-incorrect-assignments</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2830/managing-user-ids-in-fusionauth-options-for-addressing-incorrect-assignments</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[How to Resolve &#x27;Your Account Has Expired&#x27; Errors in FusionAuth]]></title><description><![CDATA[<p dir="auto">To update or extend a user’s account expiry date, you can use the FusionAuth User API to modify the <strong>expiry</strong> field. You can either set a new expiration date or set the field to <strong>null</strong> to remove the expiry entirely.</p>
<p dir="auto">Here’s an example of a <strong>PATCH</strong> request to update this field:</p>
curl --request PATCH \
  --url https://local.fusionauth.io/api/user/42661043-9ab8-4bb8-8778-85217aa05086 \
  --header 'Authorization: TulwCDDOmOtvXAVTsRUI4LfSWlF-Bd78uTnQhgviMQG9a1a3Qn7emwBn' \
  --header 'Content-Type: application/json' \
  --header 'X-FusionAuth-TenantId: 30665132-6767-6665-3132-323466613934' \
  --data '{
    "user": {
      "expiry": null
    }
  }'

<p dir="auto">Explanation:<br />
Replace the URL, user ID, and tenant ID with your instance's values.<br />
Setting <strong>"expiry": null</strong> removes the expiration date and reactivates the user account.<br />
This should resolve the issue and allow the user to log in again.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2822/how-to-resolve-your-account-has-expired-errors-in-fusionauth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2822/how-to-resolve-your-account-has-expired-errors-in-fusionauth</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Looking for docs on configuring webhook for kafka]]></title><description><![CDATA[<p dir="auto">An FYI for anyone reading this in the future. The kafka integration does have been revised and include a docker based example.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/1003/looking-for-docs-on-configuring-webhook-for-kafka</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1003/looking-for-docs-on-configuring-webhook-for-kafka</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[How can I get the system logs?]]></title><description><![CDATA[<p dir="auto">If you are running docker or some other container system where logs are written to stdout you should utilize whatever tooling exists to capture that output (<a href="https://docs.docker.com/engine/reference/commandline/logs/" rel="nofollow ugc">docker logs</a> or similar solutions).</p>
<p dir="auto">If you are using a zip file installation or some other installation method which writes log files, you can export the system logs using <a href="https://fusionauth.io/docs/v1/tech/apis/system/#export-system-logs" rel="nofollow ugc">this API call</a>.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/673/how-can-i-get-the-system-logs</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/673/how-can-i-get-the-system-logs</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[How can I use FusionAuth with OpenAPI&#x2F;Swagger clients?]]></title><description><![CDATA[<p dir="auto">Users using an sdk created by swagger can <a href="https://swagger.io/docs/specification/authentication/oauth2/" rel="nofollow ugc">use OAuth</a>.</p>
<p dir="auto">FusionAuth supports all of the grants listed there except "Client Credentials" (if that's an important grant to you, please vote on <a href="https://github.com/FusionAuth/fusionauth-issues/issues/155" rel="nofollow ugc">this GitHub issue</a>).</p>
<p dir="auto">That said, you can log a user in using this API: <a href="https://fusionauth.io/docs/v1/tech/apis/login#authenticate-a-user" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/apis/login#authenticate-a-user</a></p>
<p dir="auto">As mentioned in that document, you can require a FusionAuth API key (information about creating this here: <a href="https://fusionauth.io/docs/v1/tech/apis/authentication#manage-api-keys" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/apis/authentication#manage-api-keys</a> ) which would not be a per user API key. Or you could disable authentication for the /apilogin  endpoint:</p>
<blockquote>
<p dir="auto">Authentication may be disabled per Application, see application.loginConfiguration.requireAuthentication in the Application API or navigate to Applications  Edit  Security in the user interface.<br />
and have users authenticate against that endpoint.</p>
</blockquote>
<p dir="auto">If on the other hand you are asking about application type API keys that are managed by FusionAuth, the short answer is that is not a feature of FusionAuth.  Please see <a href="https://fusionauth.io/community/forum/topic/66/does-anyone-have-recommendations-on-how-services-should-authenticate-to-apps-that-use-fa/2">this forum post for other options</a>.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/74/how-can-i-use-fusionauth-with-openapi-swagger-clients</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/74/how-can-i-use-fusionauth-with-openapi-swagger-clients</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>