Those events without the complete suffix are sent before we commit the database transaction and the ones with complete are sent after we commit the transaction.
This means that the actual entities (user and user registration) don't actually exist when the first non-complete events are emitted.
Take a look at our Calling FusionAuth APIs In Webhooks guide for more details.
The Rolling Back From a Problematic Upgrade guide will walk you through the necessary steps.
We also recommend testing your upgrade in a non-production environment first and closely reviewing release notes to ensure you are aware of how the upgraded version of FusionAuth will interact with your integration.
Those events without the complete suffix are sent before we commit the database transaction and the ones with complete are sent after we commit the transaction.
This means that the actual entities (user and user registration) don't actually exist when the first non-complete events are emitted.
Take a look at our Calling FusionAuth APIs In Webhooks guide for more details.
In the Webhooks API, I see there are similar events with a .complete suffix. What are they for?
user.create and user.create.completeuser.update and user.update.completeuser.delete and user.delete.completeuser.registration.create and user.registration.create.completeuser.registration.update and user.registration.update.completeuser.registration.delete and user.registration.delete.completeThe Rolling Back From a Problematic Upgrade guide will walk you through the necessary steps.
We also recommend testing your upgrade in a non-production environment first and closely reviewing release notes to ensure you are aware of how the upgraded version of FusionAuth will interact with your integration.
I'm planning on upgrading my FusionAuth instance to a newer version. What can I do if something goes wrong?
Hi there!
I don't have any experience with Apache Traffic Server to be honest but are you running your FusionAuth instance with HTTPS? If so, does Apache Traffic Server trust the FusionAuth certificate?
I did manage to make it work locally by configuring the reverse proxy like shown on their docs and adding this mapping to the remap.config file:
map http://fusionauth.local:8080/ http://fusionauth-fusionauth-1:9011/
This will make it proxy requests to http://fusionauth-fusionauth-1:9011/ when it receives a request with Host: fusionauth.local:8080. Then, I added fusionauth.local to my /etc/hosts to point to Traffic Server.
This was enough to reach the FusionAuth instance, but I still needed to configure some HTTP headers to make it function correctly. Using Traffic Server's header rewrite plugin, I changed the config above to:
map http://fusionauth.local:8080/ http://fusionauth-fusionauth-1:9011/ @plugin=header_rewrite.so @pparam=fusionauth.conf
And created a fusionauth.conf file with the needed headers:
set-header X-Forwarded-Host %{CLIENT-URL:HOST}
set-header X-Forwarded-Port %{CLIENT-URL:PORT}
Please let me know if that works.
You'll receive an error in both scenarios.
If you are using the web interface, you'll get a red message saying "Already exists".
And if you are trying to use the Update User API endpoint, you'll receive a HTTP 400 Bad Request error:
Using both the UI or the API?
Even though we don't have specific SDKs for mobile apps, we do have a Flutter quickstart which uses our Dart client library.
If you want to develop natively, we recommend using AppAuth, which has iOS and Android SDKs and is maintained by the OpenId Foundation:
There's also a FusionAuth Swift Client maintained by the community.
It seems that there isn't an iOS and/or Android SDK for FusionAuth. Are there any code examples on how to use it on them?
Hi there!
Please make sure that you have selected that Lambda in your Application by navigating to its edit page, going to the JWT tab and choosing it on Access Token populate lambda.
For instance, my (extremely simple) function looks like:
function populate(jwt, user, registration) {
jwt.customClaim = 'gotcha';
console.debug(JSON.stringify(user));
}
And I received the following access token with that customClaim at the end:
