elShiaLabeouf commented on issue #6365: URL: https://github.com/apache/cloudstack/issues/6365#issuecomment-1120323557
Hi @rohityadavcloud ! Thanks for reaching out on Saturday :) You're correct, this is not a production issue, I'm using the cloudstack-simulator docker image strictly in development. The image helped me a great deal though - its out-of-box/all-in-one strategy allowed me to quickly set it up in docker-compose and move on to the development itself. Its easiness is really mind-blowing, taking into account the complexity of the project. But unfortunately, SAML SSO refused to work in the "out-of-box mode". When I found the issue, I realized that I had two options to solve it: - either the Cloudstack UI URI must be changed to "/client"; - or the cookie should be assigned to "/" Path instead of "/client" If the first option were easy, I'd've gone with that variant. But neither CS repository surfing nor examining docker image helped me with this. Plus personally, I'm not such a fan of the idea of the hardcoded cookie which forces to use "/client" path for UI if a dev wants to use SAML SSO. For the second option it was quite easy to find the code section where cookie headers are assigned and then to build a new simulator docker image to test it. For me the option of using the custom cloudstack-simulator docker image is appropriate - SAML logins in the new containers which use the new docker image work well; plain logins also work well. But I put myself in the place of a next person who is to implement SAML SSO in one's project, and I'd love to save the one from the debugging process I went through. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
