I found an env listed in the code that allows me to use Warracker like every other app.
Warracker has a built-in option to force OIDC to redirect from HTTP to HTTPS. This env is what triggers that. I knew there was something weird about this app, and this env is it.
Nine times out of ten, if I tried to migrate the database or the app, I would run into SSL issues. I ended up making a middleware in Traefik to manage the redirect, but since I'm no longer using Docker Swarm/ Docker Standalone, I was forced to figure out why Warracker would not allow proper OIDC.
The reason is that the env variable to configure OIDC over HTTPS was hidden in the code.
"FLASK_ENV": "production",
I found an env listed in the code that allows me to use Warracker like every other app.
Warracker has a built-in option to force OIDC to redirect from HTTP to HTTPS. This env is what triggers that. I knew there was something weird about this app, and this env is it.
Nine times out of ten, if I tried to migrate the database or the app, I would run into SSL issues. I ended up making a middleware in Traefik to manage the redirect, but since I'm no longer using Docker Swarm/ Docker Standalone, I was forced to figure out why Warracker would not allow proper OIDC.
The reason is that the env variable to configure OIDC over HTTPS was hidden in the code.