This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Policy test fails for user authentication.

What feature is impacted?

Policy test - when testing against authenticated user, web policy only, authenticated users filter policy (any URL)

What is the severity of the issue? (High, medium, low, minimal)

Medium

Summary of the issues:

When testing using the above settings in policy test (with fully valid URL, including protocol) we always get 'A change has occurred in the connection details, please refresh the policy test page' - refreshing the page produces the same result.


Observed behavior (What it did or didn’t do):

We are unable to confirm/test URLs against an authenticated user


Desired behavior (How is it expected to or should behave):

It should tell us if the URL is allowed or blocked for a user - Every other test works.


How do we reproduce it (Provide instructions to help us reproduce the behavior):

Log in to user portal as admin, open log viewer, and select policy test tab, Enter valid url, tick authenticated user, select web policy only test method and Authenticated users filter policy in web policy, click test, and this results in 'A change has occurred in the connection details, please refresh the policy test page'

Other (Any other detail that we need to know about):

Refreshing the page makes no difference.
We are using the STAS method of authentication against our domain controllers
We have tried firefox, edge and chrome, all produce the same result.


Supporting logs, pcaps, etc.:



This thread was automatically locked due to age.