Curious if each tenant can support having their own domain. In my can I can see using the community edition across multiple apps I have been working on, but would like, if not need, to support having something like the following:
auth.x.com
login.y.com
auth.z.ca

Where x, y, and z are different tenant TLDs. I see in the documentation that there is a "issuer" domain and theme, but I'm not sure that is an answer to this question?

Hi there,

Does FusionAuth use Elasticsearch for anything other than the administration UI? This would help me determine my potential usage and how to best host Elasticsearch for my overall needs (my apps would utilize it as well).

Thanks!

@dan Slightly? The issue would still be there should you stop supporting it/company stops existing and then while people are trying to plan out a migration a large vulnerability is found and then unfix-able. It would leave the attack vector open until a migration could occur which could be a while with small teams.

Is there a sunset provision of sorts that if the company were to fold the project would become open source so those who do depend on it can continue to maintain it or at least keep it going until we could migrate away? That right now is my last big concern.

That would be optimal. I was originally looking at running ManticoreSearch or SphinxSearch since they are generally cheaper to run and have less overhead (I can run a whole search instance for multiple apps on a 1GB VM or less vs. multiple 2 to 8 GB VMs). I don't plan on doing much, if any, extensive user searching and for what I do plan on using it can be done within my application DB and search rather than the FA instance(s).

Hi there,

Does FusionAuth use Elasticsearch for anything other than the administration UI? This would help me determine my potential usage and how to best host Elasticsearch for my overall needs (my apps would utilize it as well).

Thanks!

So would FA have an issue responding to requests from a domain different than its root domain (do you even set a root domain)?

Setting up NGINX in front of it was going to be the path I took no matter what, I just figured it would want a specific root domain or there would be a way to set root domains. My app stack requires something like the following:

Client/app -> App load-balancer (NGINX/Traefik) (SSL termination) -> Internal services

If FA isn't expecting requests to come from a specific domain, then I guess this would work fine from what you mentioned.

Curious if each tenant can support having their own domain. In my can I can see using the community edition across multiple apps I have been working on, but would like, if not need, to support having something like the following:
auth.x.com
login.y.com
auth.z.ca

Where x, y, and z are different tenant TLDs. I see in the documentation that there is a "issuer" domain and theme, but I'm not sure that is an answer to this question?