<?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 lambda]]></title><description><![CDATA[A list of topics that have been tagged with lambda]]></description><link>https://fusionauth.io/community/forum/tags/lambda</link><generator>RSS for Node</generator><lastBuildDate>Sun, 07 Jun 2026 19:34:53 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/lambda.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[How to Track Entity Changes in FusionAuth Using the Audit Log API]]></title><description><![CDATA[<p dir="auto">Yes, you would need something on your end to poll the Audit Log to fetch changes made to the Entities. Currently. there's no way to enter a log into the system logs (fusionauth-app.log) or otherwise control what goes in there. We do have a similar example for Cloudwatch on exporting Login Records to Cloudwatch which should be helpful.</p>
<p dir="auto"><a href="https://fusionauth.io/docs/operate/monitor/cloudwatch" rel="nofollow ugc">https://fusionauth.io/docs/operate/monitor/cloudwatch</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/3030/how-to-track-entity-changes-in-fusionauth-using-the-audit-log-api</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3030/how-to-track-entity-changes-in-fusionauth-using-the-audit-log-api</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Assigning Roles in FusionAuth Based on Identity Provider Login Source]]></title><description><![CDATA[<p dir="auto">This is a little tricky since a user could log in from either provider at any given time. The JWT populate lambda only has access to the user object and the registration object so you would need something on either of those to reference in the lambda. Each time a user logs in from a Identity Provider, the user in FusionAuth gets updated with the user data from the IdP. So for the JWT populate to work, you would need both providers to have a custom data field that maps to the same user.data field in FusionAuth. Then have the JWT populate Lambda map this user.data to either a custom claim or to the roles claim in the JWT, whatever works to determine the internal role on your side. Essentially this field would get updated or overwritten every time the user logs in and which would means the JWT from that login should have the correct "role".</p>
<p dir="auto"><a href="https://fusionauth.io/docs/extend/code/lambdas/jwt-populate" rel="nofollow ugc">https://fusionauth.io/docs/extend/code/lambdas/jwt-populate</a></p>
<p dir="auto">A JWT populate lambda runs whenever a JWT is minted and the reconcile lambda runs whenever a user logs in from an IdP. Which means there is a scenario if a user is logged in on both networks at the same time, it would not be accurate since the JWT from both sessions would be reading from user.data which got updated by the last IdP login. Something like the following feature would also likely be enough to solve this problem for you, we have a similar field on Webhooks but not in JWTs or Lambdas which would detail which IdP used to login.</p>
<p dir="auto"><a href="https://github.com/FusionAuth/fusionauth-issues/issues/1483" rel="nofollow ugc">https://github.com/FusionAuth/fusionauth-issues/issues/1483</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/3028/assigning-roles-in-fusionauth-based-on-identity-provider-login-source</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3028/assigning-roles-in-fusionauth-based-on-identity-provider-login-source</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[How to Block Logins Based on IdP Links in FusionAuth Without Storing API Keys in Lambdas]]></title><description><![CDATA[<p dir="auto">Currently, FusionAuth lambdas cannot call the API without including an API key in the code — there’s no built-in secret manager for this yet (feature request).</p>
<p dir="auto"><strong>Alternative approaches:</strong></p>


<p dir="auto"><strong>Webhook filtering (recommended)</strong><br />
Use the <strong>user.login.success</strong> webhook to check if the user is linked to an IdP, and reject the login by returning a non-200 response. This avoids storing API keys in lambdas, but adds an extra network call to each login.</p>


<p dir="auto"><strong>Store link data in</strong> user.data<br />
Push IdP linking info into a custom <strong>user.data.links[]</strong> field so it’s accessible in most lambdas without needing an API call. You’ll need a process to keep this data current.</p>


]]></description><link>https://fusionauth.io/community/forum/topic/3023/how-to-block-logins-based-on-idp-links-in-fusionauth-without-storing-api-keys-in-lambdas</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3023/how-to-block-logins-based-on-idp-links-in-fusionauth-without-storing-api-keys-in-lambdas</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Why FusionAuth Webhooks Show ONE_TIME_PASSWORD Authentication Type for Logins]]></title><description><![CDATA[<p dir="auto">Great question—this often causes confusion.</p>
<p dir="auto">In FusionAuth, logging in after a <strong>Forgot Password</strong> flow is tracked as <strong>ONE_TIME_PASSWORD</strong>. That’s because, technically, FusionAuth uses a one-time password during that process. For example, if you look at the <a href="https://fusionauth.io/docs/apis/users#change-a-users-password" rel="nofollow ugc">Change a User’s Password API</a>, it returns a one-time password token. On the hosted pages, FusionAuth automatically consumes this token to sign the user in immediately after they reset their password via the forgot password link in their email.</p>
<p dir="auto">So even without traditional OTP or MFA configured, these login events can appear as <strong>ONE_TIME_PASSWORD</strong> due to password reset flows.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/3004/why-fusionauth-webhooks-show-one_time_password-authentication-type-for-logins</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3004/why-fusionauth-webhooks-show-one_time_password-authentication-type-for-logins</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[How to Retrieve and Replay Failed Webhook Events in FusionAuth]]></title><description><![CDATA[<p dir="auto">FusionAuth provides an API to <strong>search for webhook event logs</strong>, including failed events. For example, you can use this endpoint:</p>
<p dir="auto"><strong>/api/system/webhook-event-log/search?start=&lt;timestamp&gt;&amp;end=&lt;timestamp&gt;&amp;eventResult=Failed</strong></p>
<p dir="auto">This will return all webhook events in the specified time frame that failed. More details are here:<br />
<a href="https://fusionauth.io/docs/apis/webhook-event-logs#search-webhook-event-logs" rel="nofollow ugc">Search Webhook Event Logs</a></p>
<p dir="auto">In the API response, the <strong>event</strong> section contains the original payload that was sent. While FusionAuth <strong>doesn’t currently have a built-in replay feature</strong>, you can extract this event data and <strong>manually re-send</strong> it to the webhook URL using your own REST calls.</p>
<p dir="auto">A native replay feature is on the roadmap, but there’s no confirmed timeline for its release yet.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2991/how-to-retrieve-and-replay-failed-webhook-events-in-fusionauth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2991/how-to-retrieve-and-replay-failed-webhook-events-in-fusionauth</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Determining User Authentication Method in FusionAuth]]></title><description><![CDATA[<p dir="auto">Yes, FusionAuth provides this information via the <strong>authenticationType</strong> claim in the JWT. This claim indicates the authentication method used, such as <strong>PASSWORD</strong>, <strong>GOOGLE</strong>, <strong>SAML</strong>, etc.</p>
<p dir="auto"><strong>How to Access Authentication Type</strong>:</p>

<strong>From the JWT</strong>:

The <strong>authenticationType</strong> claim is included in the <strong>JWT access token</strong>.
Documentation: <a href="https://fusionauth.io/docs/lifecycle/authenticate-users/oauth/tokens#access-token-claims" rel="nofollow ugc">JWT Access Token Claims</a>


<strong>From a Webhook Event (Alternative Approach)</strong>:

The same <strong>authenticationType</strong> value is included in the <strong>user.login.success</strong> webhook event.
This may be useful if your system processes authentication events via webhooks instead of decoding JWTs.
Documentation: <a href="https://fusionauth.io/docs/extend/events-and-webhooks/events/user-login-success" rel="nofollow ugc">User Login Success Webhook</a>



<p dir="auto">For additional details on JWT structure and claims, refer to: <a href="https://fusionauth.io/articles/tokens/jwt-components-explained#the-jwt-token-body" rel="nofollow ugc">JWT Components Explained</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/2933/determining-user-authentication-method-in-fusionauth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2933/determining-user-authentication-method-in-fusionauth</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Determining User Authentication Method in FusionAuth]]></title><description><![CDATA[<p dir="auto">Yes, FusionAuth provides this information via the <strong>authenticationType</strong> claim in the JWT. This claim indicates the authentication method used, such as <strong>PASSWORD</strong>, <strong>GOOGLE</strong>, <strong>SAML</strong>, etc.</p>
<p dir="auto"><strong>How to Access Authentication Type</strong>:</p>

<strong>From the JWT</strong>:

The <strong>authenticationType</strong> claim is included in the <strong>JWT access token</strong>.
Documentation: <a href="https://fusionauth.io/docs/lifecycle/authenticate-users/oauth/tokens#access-token-claims" rel="nofollow ugc">JWT Access Token Claims</a>


<strong>From a Webhook Event (Alternative Approach)</strong>:

The same <strong>authenticationType</strong> value is included in the <strong>user.login.success</strong> webhook event.
This may be useful if your system processes authentication events via webhooks instead of decoding JWTs.
Documentation: <a href="https://fusionauth.io/docs/extend/events-and-webhooks/events/user-login-success" rel="nofollow ugc">User Login Success Webhook</a>



<p dir="auto">For additional details on JWT structure and claims, refer to: <a href="https://fusionauth.io/articles/tokens/jwt-components-explained#the-jwt-token-body" rel="nofollow ugc">JWT Components Explained</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/2881/determining-user-authentication-method-in-fusionauth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2881/determining-user-authentication-method-in-fusionauth</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Invalid Date</pubDate></item><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[How to get populated user.data after user registraion.]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/1292">@muravyov-alexey</a> Thank you!</p>
]]></description><link>https://fusionauth.io/community/forum/topic/1443/how-to-get-populated-user-data-after-user-registraion</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1443/how-to-get-populated-user-data-after-user-registraion</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Lambda reconcile does not remove role from registration]]></title><description><![CDATA[<p dir="auto">Hi <a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/717">@tl-fa</a>,</p>
<p dir="auto">You can view our <a href="https://fusionauth.io/docs/v1/tech/core-concepts/roadmap/#overview" rel="nofollow ugc">Roadmap Guidance</a> regarding how features are implemented into FusionAuth.  A good snapshot of current development can be found <a href="https://github.com/FusionAuth/fusionauth-issues/projects/2" rel="nofollow ugc">here</a> as well.</p>
<p dir="auto">We will certainly update any related issue cards as development moves forward!</p>
<p dir="auto">Thanks!<br />
Josh</p>
]]></description><link>https://fusionauth.io/community/forum/topic/939/lambda-reconcile-does-not-remove-role-from-registration</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/939/lambda-reconcile-does-not-remove-role-from-registration</guid><dc:creator><![CDATA[joshua]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Can I register a user for additional applications in a SAML reconcile lambda]]></title><description><![CDATA[<p dir="auto">Nope. While you can modify attributes of the user object and the changes will be persisted, you can't modify the registrations of that user.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/825/can-i-register-a-user-for-additional-applications-in-a-saml-reconcile-lambda</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/825/can-i-register-a-user-for-additional-applications-in-a-saml-reconcile-lambda</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Kickstart and lambdas and newlines]]></title><description><![CDATA[<p dir="auto">Can you use an include for the function body? For example: (where myLambda.ftl is your Lambda function in a folder named lambdas)</p>
"lambda":{
   "body":  "@{lambdas/myLambda.ftl}",
}

<p dir="auto">That should preserve your line returns if you include it that way. Hope that helps!</p>
]]></description><link>https://fusionauth.io/community/forum/topic/232/kickstart-and-lambdas-and-newlines</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/232/kickstart-and-lambdas-and-newlines</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Can we set multiple &quot;aud&quot; claims in FusionAuth?]]></title><description><![CDATA[<p dir="auto">We do not support this directly in FusionAuth, but you could use a Lambda to set the aud claim to whatever you want.</p>
<p dir="auto">The specification allows for a string value, or an array of string values, so you could create a Lambda with something like: jwt.aud = [ 'foo', 'bar' ];</p>
<p dir="auto">More about Lambdas and JWTs here: <a href="https://fusionauth.io/docs/v1/tech/lambdas/jwt-populate" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/lambdas/jwt-populate</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/52/can-we-set-multiple-aud-claims-in-fusionauth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/52/can-we-set-multiple-aud-claims-in-fusionauth</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>