Replies: 1 comment 2 replies
-
an you provide your docker-compose.yml or docker commands and your nginx config? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I've recently been trying to setup STIG Manager with the api, authentication, and MySQL containers behind a Nginx docker container within a test environment on a RHEL VM but have not had success yet. The goal is to use username/password authentication and to support TLS on port 443.
I have attempted to use the setup provided in https://github.com/NUWCDIVNPT/stigman-orchestration but it has not worked as intended as I continue to receive errors for the STIG Manager web app being unable to communicate with the authentication provider despite all containers being able to communicate with each other using the hostnames provided in the docker-compose file. I have changed the values of STIGMAN_CLIENT_OIDC_PROVIDER, KC_HOSTNAME_URL, and KC_HOSTNAME_ADMIN_URL to reflect the external URL of the server that it is being hosted on. Additionally redirects from the main stig manager web app to the OIDC provider appear to be dropping https for http. I have done my best to follow the documentation provided stig-manager.readthedocs.io and previous discussion posts.
Are there any examples of this setup or similar using an external IP that are working? All examples that I have found that were mentioned in previous discussion posts have had the same issues.
Thank you for your time!
Beta Was this translation helpful? Give feedback.
All reactions