The cross domain error would be occurred on Silverlight. Because distinct URL has been configured on session central service, session service and run time service.
Summary: An error occurred while initializing communication with the server.
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.41212.00&File=System.ServiceModel.dll&Key=CrossDomainError
For example I have configured session central and session service with out SSL and runtime service with SLL, in my scenario looks like;
Here the service URL has been configured in same domain.
http://gpserver:48650/SessionCentralService (without SSL)
http://gpserver:48651/SessionService (without SSL)
https://webclient.sathiya.local:48652/ (SSL mandatory for GP web client Runtime service)
If suppose the web client is accessible thought internet and configured public url then the Runtime service will be configured like https://public.sathiya.io:48652/.
So the silver light wont communicate between cross domains.
http://gpserver:48650/SessionCentralService (Local url)
http://gpserver:48651/SessionService (Local url)
So you have to configure all three service url should be in same domain. Either it would be local FQDN urls or public urls,
https://webclient.sathiya.local:48650/SessionCentralService (without SSL)
https://webclient.sathiya.local:48651/SessionService (without SSL)
https://public.sathiya.io:48650/SessionCentralService (Local url)
https://public.sathiya.io:48651/SessionService (Local url)
Security issue may happen after installed this setup. To resolve Web client error with SSL/TLS