-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SAML issue #30
Comments
Hi, Sorry, I am not very familiar with SAML, but I'll try to assist as much as possible. My first instinct would be that there are two versions of the saml extension in the extensions directory. If you pulled the image I uploaded a few days ago, make sure to delete all references to version 1.5.3 in the directories extensions and extensions-available. Can you also post the full version of the log? I'll also look at the mailing list to see if a similar issue has been reported already. Cheers Antoine |
As requested `s6-rc: info: service s6rc-oneshot-runner successfully started ` |
So it's not an issue of duplicate extensions... On one side, it's good, it means my cleanup routine works, on the other hand, that does not solve your issue... You could try to move the saml configuration into your guacamole.properties. Passing parameters as environment variables is not trivial, and needs to be coded variable by variable. EDIT: I confirm that moving the SAML configuration to guacamole.properties makes progress. The exception is not raised anymore, but I cannot go further as I cannot use your URLs. But I confirm this is a way to try. For info, it takes more than 1200 lines of code for the official Guacamole image to deal with environment variable. I know this is something I should do, but I don't know when I would find the time to do this... |
Evening,
I'm trying to connect to Azure AD using SAML. I've set everything up but am getting the following error
I'm not sure where to find further logs or if I'm missing something obvious. A copy of my compose file is below
The text was updated successfully, but these errors were encountered: