I’ve discovered that the Azure Enterprise application breaks with the enterprise version. Within the enterprise version I can test SSO, and it works, however actually using SSO fails because it looks like the redirect URL’s have been hard coded in the enterprise version to use http.
In the SAML connector in the community version, I see the Redirect URLS listed like:
Also, on the community version the Sign SAML Request is enabled even though I haven’t entered x509 certs or keys (and it works fine). If I toggle the Sign SAML on the enterprise version it forces me to enter x509 cert and key, but I’m not currently using that.
Just following up on my own question, so deploying the code directly does not have the same problem, this was only using the virtual machine available for deployment.
Hello Tim,
What URL you have in Cron url setting? (Settings/crontab)
Regarding Signed SAML request, so if you enable this option eramba ask you to put certificate and key. That sound correct to me. (I would say there is a bug on community that these fields are not mandatory)
It works fine on installing the source code so not sure its worth digging into it, this appears to be only the VM appliance with an SSL cert installed (Let’s Encrypt).