FusionAuth Running In Azure Container App Environment

alan.rutter

Hi,

I am trying to use FusionAuth (via docker image) in a Microsoft Azure Container App Environment. I am using a Microsoft Azure PostgreSql Flexible Server instance to host the database - after much hassle getting Private Endpoints etc configured, I can access the FusionAuth container and configure it.

I get an error though - the same as here and I was wondering if there has been any progress made by the FusionAuth team on making this an 'easy' fix as running inside containers is more prevalent these days.

I also have an instance of KrakenD API gateway running inside my container app environment - would I be able to use it to proxy FusionAuth calls and add any missing headers. KrakenD can do authentication using Keycloak/Auth0 etc - would this be a possibility?

Looking for some real world help on my options.

Thanks
Alan

alan.rutter

Here's where I am at. I have a FusionAuth instance running on Azure giving me a Proxy Configuration Warning error. I thought I would try accessing the FusionAuth instance via my KrakenD API Gateway.

I added some rules to access the /admin path and although it displays the login screen, none of the query parameters are set and I don't see any of the redirects from admin to admin/login and outh2/authorize as I do if accessing FusionAuth directly.

I am assuming that this may be because I need to add KrakenD as an application but I'm not really sure. Anyhow, I can't add an application because of the Proxy error - catch 22.

I would greatly appreciate some input from the FusionAuth team on how I can make this work from Azure Container Apps. FusionAuth is a great product, but if it can't be used from within Azure Container Apps, then it will not receive the uptake it deserves from developers who will abandon it for something that does play nice.

At the moment, reluctantly I may need to do that as getting it to work is too much of a headache and there are project timeframes to be met.

Regards
Alan

dom9

Hello there,
I feels like you are encountering some complex issues with running FusionAuth in Azure Container Apps and using KrakenD as a proxy.

For the Proxy Configuration Warning, be ensure that your FusionAuth instance is aware of the correct external URL and headers. You might need to set the FUSIONAUTH_URL environment variable appropriately.

Releated KrakenD, you could configure it to correctly handle the necessary headers for FusionAuth. Be sure your KrakenD configuration includes the necessary routes and headers for FusionAuth's admin and OAuth endpoints.

Consider checking the FusionAuth and KrakenD documentation for any specific configurations needed for Azure environments.

If the issue still did not get solved, you might want to reach out to FusionAuth support directly for more tailored assistance.

Hope it helps.