Zanyterp, I have one more question for you if you don't mind. Can I ask why a sign-in URL can only point to a single realm, when SAML authentication is configured (see KB link below)? We have realm authentication policies setup so even though one sign-in URL points to two realms (one of the realms being a SAML auth realm), through authentication policies it only evaluates to one realm? Shouldn't this meet the criteria of the sign-in URL only pointing to a single realm and thus SAML auth should work? What we are finding is that the authentication policies work, it only redirects the user to the appropriate realm as directed by the authentication policy, however, in the realm with SAML authentication, we find that we get Invalid/Missing Sign-IN URL errors. The other authentication realm works great. Also important to note that both work independently with their only sign-in URL if configured that way. It *seems* that Juniper only wants ONE realm (apparently it won't work with two realms, even if the auth policies make them mutually exclusive of each other so that only one realm kicks in for one sign-in URL). I'm trying to figure out why this won't work.... unless it should? Hopefully this makes sense. http://kb.pulsesecure.net/InfoCenter/index?page=content&id=KB22270&actp=RSS&smlogin=true Thanks!
... View more
