Replies: 2 comments
|
Hi @rodjul, Thank you for the feedback and for the proposal. I know that requiring to build the container just to configure the ACS URL is not a practical experience, especially for self-hosted deployments. The idea of introducing a new environment variable to dynamically set the ACS URL makes a lot of sense, so I've created a GitHub issue to track this improvement for a future release: #10533 If you'd like to contribute and tackle this yourself, we'd absolutely welcome a Pull Request! Feel free to jump in, the community's contributions are always appreciated 🙌 Thanks again for raising this! |
0 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,
Given this issue #9724 and the solution https://docs.prowler.com/troubleshooting#saml/oauth-acs-url-incorrect-when-running-behind-a-proxy-or-load-balancer, turns out that this solution, in my opinion, is not practical just to set an URL to configure SSO. This introduces to me a new process that we will have to build a custom container for the frontend and manage it.
What I would like to propose is the possibility to set a maybe new environment to configure this setting of ACS URL.
If anyone has a better idea other than to build a custom container, just to allow this setting to be dynamically, it would be great!
Thanks
All reactions