Hi Ross,
This is a known bug and we've been trying to fix it. We have an internal build with a fix for this that will be published soon.
There are some work arounds:
- If you're using a local instance of WAC on your own container host, you can change the username/password to manage the server on WAC's landing page. See that you can continue to use the same user, just provide the username and password manually, rather than SSO.
- You can use the browser from another machine while still keeping the WAC instance on the same container host. In this case you can use SSO.
- You can install WAC on another machine and target the container host remotely (This is recommended for production scenarios). In this case you can use SSO.
Hopefully this will be fixed soon.
Regards,
Vinicius.
Twitter: @vrapolinario