You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proxies have been a hot topic lately. Even though proxies just sit in front of FA I wonder if we should have some documentation to help them feel confident in how they're setting up their proxy in regards to FA. F5 is another one that has come up recently.
CAA's use case was that they have an app where traffic goes through. Domain goes through F5 and the Azure site locks down IP addresses. Essentially they'd provide us a list of F5 static IPs for both the API and hosted login pages.
The text was updated successfully, but these errors were encountered:
we did quite an extensive guide here https://fusionauth.io/docs/extend/examples/api-gateways/cloudflare-api-gateway, but I think the use case here is the opposite (putting Cloudflare in front of Fusionauth instead of protecting a Cloudflare worker with Fusionauth). We can definitely do a guide on how to set up Cloudflare in front of Fusionauth, but probably this is something that better lives in the Cloudflare docs?
We often have a problem of 'how much of someone else's platform do we document', so let me know if you have inputs on the balance here. We could just do this and find the best existing cloudflare docs to link to, or we could have it all live on Fusionauth, and take all the screenshots etc of the cloudflare setup.
Proxies have been a hot topic lately. Even though proxies just sit in front of FA I wonder if we should have some documentation to help them feel confident in how they're setting up their proxy in regards to FA. F5 is another one that has come up recently.
Cloudflare has been commonly asked about - looks like the only doc that comes up in Kapa is https://fusionauth.io/community/forum/topic/328/does-fusionauth-integrate-with-cloudflare
CAA's use case was that they have an app where traffic goes through. Domain goes through F5 and the Azure site locks down IP addresses. Essentially they'd provide us a list of F5 static IPs for both the API and hosted login pages.
The text was updated successfully, but these errors were encountered: