I tested deploying this artifact to a Super.Human.Installer Domino instance for #15. Unfortunately, this failed with a CORS error on the agent calls. The agent calls use http://127.0.0.1:8080, but the Super.Human.Installer server should be called with a domain name. The default is https://domino.demo.startcloud.com, but the user is allowed to choose other names.
To allow this to work, I had to change the URL at two locations:
I had similar problems on domino-49. Can we make these paths relative to the server base (i.e. /Super.Human.Portal.nsf/XMLAuthenticationTest?OpenAgent) so that we don't need to change this? The Genesis installer for #15 won't necessarily know the base FQDN of the generated server.
I tested deploying this artifact to a Super.Human.Installer Domino instance for #15. Unfortunately, this failed with a CORS error on the agent calls. The agent calls use
http://127.0.0.1:8080
, but the Super.Human.Installer server should be called with a domain name. The default is https://domino.demo.startcloud.com, but the user is allowed to choose other names.To allow this to work, I had to change the URL at two locations:
I had similar problems on domino-49. Can we make these paths relative to the server base (i.e. /Super.Human.Portal.nsf/XMLAuthenticationTest?OpenAgent) so that we don't need to change this? The Genesis installer for #15 won't necessarily know the base FQDN of the generated server.
Originally posted by @JoelProminic in https://github.com/Moonshine-IDE/Super.Human.Portal/issues/14#issuecomment-1513856607