Deployment
FoxIDs supports multiple deployment options and you can host it yourself either in the cloud or on-premises.
- Deploy using Kubernetes on-premises or in the cloud
- Deploy using Docker on-premises or in the cloud - primarily for dev and test
- Deploy on Windows Server with IIS
- Deploy in Azure App Service Container
Alternatively, use FoxIDs Cloud.
New FoxIDs releases are published continuously. Make sure to update your installation regularly to stay up to date with the latest improvements and fixes.
The Docker image registry is available at www.foxids.com. Deployment components can be downloaded for each release, and the corresponding Docker images are listed alongside the release details.
After deployment, consider:
- Place your FoxIDs deployment securely behind a reverse proxy.
- Trust an internal root CA in Kubernetes when internal TLS is terminated and re-issued by a proxy. Kubernetes internal CA.
- Improve the password quality by uploading risk passwords.
- Configure monitoring.
- Upload your users from a CSV file, with or without a password.
PostgreSQL connection strings
When using PostgreSQL, we recommend setting Enlist=false explicitly in the connection strings for both FoxIDs and FoxIDs Control:
Host=localhost;Username=postgres;Password=<password>;Database=FoxIDs;Enlist=false
Existing installations can keep their connection strings unchanged. Both Enlist=true and Enlist=false are supported.
Setting Enlist=false disables automatic enlistment in .NET transaction scopes. With Enlist=false, account moves caused by email changes are not atomic. If saving the updated account fails, FoxIDs attempts to restore the original account; a process interruption or a concurrent identifier conflict can prevent restoration.
Set Enlist=true to use a transaction for these account moves. If Enlist is omitted, Npgsql uses true by default.