Keycloak fails to initialize at login, I'm guessing because Storware is attempting to show it in an iframe. The console is throwing an error that it cant display keycloak in an iframe because it's header is set to same as origin.

As far as I'm aware the "sameasorigin" header is best practice especially when dealing with services that handle sensitive data. The only way around this would be using a subdomain of storware's dns\domain name as the keycloak url.

Is there any reason why an iframe is even being used at the login page? With all the services I've integrated with keycloak, none of them have needed to display it in an iframe.