SSO Testing. Here is what we did: When we recently changed the way we validate SSO (we use a Microsoft Azure application provided by WorkFront) we made the change on a weekend; When we made the change, I logged out and tried to log in using on-VPN SSO ("http://company.attask-ondemand.com/">http://company.attask-ondemand.com/ ). I got an error. I was on a Webex and everyone could see the Azure error in the lower right corner. Another change was made, I tried to log in again. Another error. More error message analysis. It took about 20 minutes of error message analysis and tweaking until I could log in; Once I could log in, I asked everyone on my team to try to login using on VPN SSO access, it worked for everyone; I tried to log in on VPN, not using SSO, Azure asked me to authenticate, it worked ("http://company.attask-ondemand.com/login)">http://company.attask-ondemand.com/login) ; I dropped off the company VPN and tried to SSO in, Azure asked me to log in, it worked (correct behavior); I dropped off the company VPN and tried to login without SSO ("http://company.attask-ondemand.com/login">
http://company.attask-ondemand.com/login ), it worked; I tried to log in without VPN with a bogus ID, WorkFront wouldn't let me in (correct behavior); Those were the four use cases. The two binary variables are: Login with SSO or not; Login with VPN or not; Hope that helps. Eric