Topics created by elliotdickison

@stefan-0 I tried to test this out on my own. I set up a webhook that I know worked, then changed the url so it would fail. Here is the log from the failed attempt.

Screenshot 2024-12-20 at 2.47.49 PM.png

Then I go to the Webhook log and see:

Screenshot 2024-12-20 at 2.49.07 PM.png

If I dig into the one that failed, I see:

Screenshot 2024-12-20 at 2.49.53 PM.png

Notice the ID in the general event is:
Id [9f9faf2d-7d32-48ce-98ee-76a31c43cac2]

And in the source of the Webhook Log, you see the id is:
"id" : "9f9faf2d-7d32-48ce-98ee-76a31c43cac2"

Hope this helps.

@elliotdickison Check out these posts:

179 and 2485

Wonderful blog post. I found it very helpful and informative. Solar

@elliotdickison Thanks for posting!

I shared this internally.

Regarding your first point, I agree a table would of MAU/$ would be helpful.

Regarding your second point, really appreciate that (and the feature suggestions/bug reports you make!). We discuss features and pricing pretty regularly, and I'll surface this comment next time we do so.

@vatsal We did not

@elliotdickison

We typically see the chokepoints for FusionAuth in either the CPU (when doing a lot of password hashing) or the database.

More here: https://fusionauth.io/docs/v1/tech/installation-guide/monitor/#load-testing

Since usage varies, I suggest you perform your own load testing to determine connection limits. Would love to see your conclusions!

@elliotdickison said in Awkward OAuth logout in mobile app:

@maciej-wisniowski We ended up going with your solution and it's working alright, thanks for that!

@robotdan One suggestion for you all: I found the naming of the "AllApplications" value for the application.oauthConfiguration.logoutBehavior setting a bit confusing. As far as I can tell all the "AllApplications" value it really means is "show the OAuth2 logout page". That page can be used to log out of all apps (that's the default template behavior), but it doesn't have to be used that way. Per the suggestion from @maciej-wisniowski we are using the page to log the user out of only one app and show a "successfully logged out" message. Maybe to avoid a breaking API change the value "OneApplication" could be added in addition to "AllApplications" and "RedirectOnly". That value could use the same OAuth 2 logout template but maybe set a variable that could be used to conditionally turn off the logout-of-all-apps behavior. Just a thought.

Thanks for the suggestion @elliotdickison - please do open a GH issue with this suggestion and how you'd like the logout to behave in your use case.

@elliotdickison

Have you had a chance to review our documentation on setting up themes and localization here?

https://fusionauth.io/docs/v1/tech/themes/localization/

Thanks,
Josh

@elliotdickison,

What you are looking for is some of the Auth Flows that we have outlined (pay attention to the recommended ones for a secure setup). Specifically, this one might be helpful.

The common pattern is to have a BFF (backend for frontend) to keep things secure.

We have a nice example of how to securely complete the OAuth handshake in our 5-minute guide, with a section on how to use cookies. I would start there for an overview on how to complete the OAuth handshake using express and nodeJS.
https://fusionauth.io/docs/v1/tech/5-minute-setup-guide#cookies-for-a-single-page-application

I hope this is a good starting point. Let us know if you have other questions.

Thanks,
Josh