When you attempt to login, it will access xmlsocket://theurlyouspecified:5229
The enterprise plugin listens on that port, and returns a crossdomain file that should allow access. Apparently something isn’t working there; I will investigate.
We have our server thinking it’s just “domain.com” so that all of the users can login using their email address, instead of user@chat.domain.com. However we access our server via chat.domain.com.
When I go to the sparkweb login page, the server field is prefilled with domain.com. When I changed this to chat.domain.com, it worked perfectly.
One of the things I’m hoping to add for the next version (tons of stuff already on the list, so no promises) is better admin-side configuration of what to show, what to prefill, etc…
I’ll think about what to do about this issue; one of the fixes made late in the beta process is that once logged in, sparkweb will use the server’s domain name even if it’s different from the domain used to log in (so even if you logged in with the server’s ip address, you’d still be listed as name@domain). This is somewhat different from that though… perhaps I could check a couple of different options to see which one(s) have a crossdomain with the right settings available.