Відео

"starting with FusionAuth self hosted Community plan and moving to hosted plans a offers a better route to align needs and capacity costs in the long term. Definitely my first choice for future potential business ventures." -- Awesome to hear, we agree. Good insight with the .NET auth. story. Keeping an eye on it. Not sure what you mean a "plan to target...." In general, we try to make the developer community aware of our product offering and pricing (finding the right level of licensing and support for your situation, as you mentioned above). Once they understand that, they can make the right decision for themselves and we are here for them. "What's the risk of FusionAuth being acquired by evil corp A / B /C..." While I can't say the risk is zero throughout the rest of time, we like our business model and service. It has made us successful and who we are today as a company. As a business we want to continue being successful and grow while providing great service and an outstanding product at a price point that makes sense. In the small chance that something like an acquisition by an evil company happens, we fully expect our customers and community to hold us accountable and that's why I don't think something like that is going to happen. And if you are really worried, one of the nice things about FusionAuth is that you can grab all your data any time you need.

Well said!

Thanks for the feedback.

Loud as compared to what other videos? We can take a look into it.

The video is trying to convey a lot of information quickly and effectively. We will take the feedback into consideration. Thanks for checking out the videos.

CAPTCHA is used as a security measure to distinguish between human users and bots. I am sorry to hear you had a terrible experience. Whatever actions you were taking must have been similar to actions a bot might take. If you contact support and explain what you were trying to do, they may be able to help prevent so many showing up in the future.

Occasionally Mr. Bachman shows up around these parts.

Glad it was helpful! 🎉

Nice, we hope your login is easy :D

Wait until our next release, it is going to be super easy to theme them on your own!!

If you are trying to secure your backend and require the use of an API key this might be best. If you are just basing it on purly the JWT you could base it on the issuer, audience, and any claims you need to guarantee the call is safe. You can see more on how to accomplish Authorization and Securing your Application fusionauth.io/docs/get-started/core-concepts/authentication-authorization#authorization-and-securing-your-application

FusionAuth has two types of self-service registration, Basic and Advanced. The Basic is free with all plans. The Advanced registration requires a paid plan. fusionauth.io/blog/announcing-fusionauth-1-47#preferred-languages-on-the-basic-registration-form has a little more info for you if you are interested.

Great suggestion! Added the link for react blog on oauth.

You may want to check if you have any firewalls up and running. Are you able to log into the admin interface OK? If you'd like some help troubleshooting, please let us know.

@@FusionAuth Thanks, I diagnosed it, I was using localhost:9011 instead of fusionauth:9011 since my backend app and fusionauth was dockerized with docker compose. So it was more of a networking issue and using service name instead of hostname (in my dockerized backend container localhost refers to the container and since I was using localhost it was not able to connect to port 9011 on the container and that was absolutely correct, but when I use service name docker knows how to proxy my request from my backend container to fusionauth container)

I think that is addressed at about 1:50 in the video. Are you looking for something else?

@@FusionAuth Thank you but it would have been better if you added one additional fields and show how the exported users list looks like

Depends what you mean by token management. For the most part, it does handle getting the token and information from it into objects you can use.

FusionAuth doesn't support RADIUS at this time. Please feel free to file a feature request here: github.com/fusionauth/fusionauth-issues/issues We do support LDAP through our connectors, a paid edition feature. More here: fusionauth.io/docs/v1/tech/connectors/ldap-connector/

thanks!

According to the documentation firebase.google.com/docs/auth/admin/manage-users you can access that information so you should be able to pull that over.

Hi! Have you managed to do that? I'm trying to do the same thing or to sort them by the date they signed up, but I can't find the way to do it.

and so do you!

Sure, there are a number of community supported reverse proxy configuration examples here: github.com/FusionAuth/fusionauth-contrib/tree/master/Reverse%20Proxy%20Configurations There's also a reverse proxy guide here: fusionauth.io/docs/v1/tech/admin-guide/proxy-setup

@@FusionAuth Thank you so much for your response. Ill check it out asap.

@@TheGreatestMajesty great! Let us know if you have other questions.

Hiya, usually it is cookie based for web apps. For a mobile app it might be some other unique device indicator.

Would you mind heading over to fusionauth.io/community/forum/ and sharing some of the code you are trying to use to populate the custom claims and the code to read them in the application?

That is great news! Hopefully it is just adding to that book of knowledge 😉

Glad you liked it!

Glad it was helpful!

Glad you liked it!

Sure. You can view the code here: github.com/fusionauth/fusionauth-example-react-native-0-71

Hmmm. Cookies should be stored in the system browser. How are you accessing the authenticated website? Also, how does the authenticated website check for if a user is logged in?

It is probably our favorite type of knob for sure!

Thanks MPR. It's a bit confusing, but in this video a UUID is used as an API key value. Any string can be an API key value (a UUID, 'super-secret' or a high entropy string). We agree it is confusing.

Firebase user ids are random strings, but FusionAuth user ids are UUIDs. So each user who is imported will have a UUID assigned, as well a firebase id stored in the FusionAuth user.data field. You can query on the latter, but the former is what will be used for all operations requiring a user id. Does that help?