Multi-domain SSO is a big concern for us right now, especially as we've been merged into a larger company. I suddenly have teams coming from 20 different domains, and because the main master Sauce Labs account is locked down to one SSO domain, there are teams that can't run a test right now. I've heard they're working on a solution and they've been very communicative with us about it. A solution to that would help us a lot. The other issue is that when you're behind a corporate proxy and inside a corporate network, it's a nightmare in general. And the problem that we've come up against over and over again is that a lot of our network staff don't want to open up giant CIDR blocks to internal traffic. Opening it up to one endpoint which is Sauce Labs, through a little API is perfectly fine. That's one IP address and it's no big deal. But for their virtual machines they have one jump box and that jump box contains an entire CIDR block that changes each time the tunnel starts up. In other words, if every call went into one IP and that got bounced back to a load balancer or net gateway, that would help a lot too. When I go to the network team and say, "Hey, we're using a product, a piece of software, and I need an entire CIDR block opened," the first and almost eternal response to that will be "absolutely not." Getting things set up and running is always going to be a bit of a struggle within any corporate environment. Most of that is not Sauce Labs' fault, but the things I just mentioned are things they could do to help deal with that struggle.
