8GB is way plenty. 1 or 2GB is generally adequate, it can depend a bit, but FusionAuth doesn't keep much in RAM. Scaling out horizontallly is likely more effective than more ram per instance. This way you can handle more logins per second--these are going to be cpu bound.

That message means the user is not registered for the application you’re logging into. If you create a registration for the user you’ll see Authenticated.

More on this here: https://fusionauth.io/community/forum/topic/5/can-you-limit-a-user-s-login-authentication-access-to-applications-within-a-single-tenant/2

This is not currently available.

The plan is to build out SMS templates that can localized and customized but no timelines have been determined.

If you have purchased a high availability hosting plan we can configure additional URLs for you - such as login.example.com - and then FusionAuth would be in the same domain as your own application, and you'd be able to verify the domain.

@chakshu

Sorry, I pointed you to the incorrect setting.

You can go to Applications > FusionAuth > Edit > JWT > Refresh Token duration

Changing that to 1 (the value is in minutes) caused me to be signed out of the admin application after 60 seconds.

Hope that helps.

If you use the advanced registration forms, you can edit user data now. This was recently released as a premium feature (requiring a paid license; more info here).

More info on setting up the user data editing screen: https://fusionauth.io/docs/v1/tech/guides/advanced-registration-forms/#editing-user-data-in-the-admin-ui

It depends, if you’re on an Enterprise hosting plan we can configure a certificate with your domain. So if your app is running at acme.com - we can add a certificate so that you can create a DNS CNAME record to our service using login.acme.com (for example) .

More on our plans here: https://fusionauth.io/pricing

We have load tested our medium deployments to roughly 20 logins per second. It can vary quite a bit. We ship with PBKDF2 and a factor of 24,000. That configuration is the primary limiter to how many passwords we hash per second.

Tune it up to bcrypt factor 14, and it may take 3-5 second per hash. You can also tune the factor down from the default scheme to increase logins per second - it is a trade-off between security and performance.

And you can change these settings at the tenant or user levels: https://fusionauth.io/docs/v1/tech/apis/tenants
https://fusionauth.io/docs/v1/tech/apis/users