Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Security > Proxy user authentication > Multiple realm authentication > Troubleshooting Multiple Realm Authentication
*
Users are not challenged when a challenge is expected
*
Users are challenged when no challenge is expected
1.
The rules in filter.config are checked and applied. This action occurs as a first step in every type of Content Gateway user authentication. If a filtering rule is matched, the rule is applied and user authentication processing stops. See Filtering Rules.
Confirm that there is no unexpected matching of a filter.config rule. Among other purposes, filter.config rules can be used to bypass user authentication. See Filtering Rules.
*
In Content Gateway Manager, go to Configure > My Proxy > Basic, scroll to the bottom of the page and verify that Read authentication from child proxy is enabled. If it's not, select On, click Apply, and then restart Content Gateway.
Warning 
Debug log information is written to: /opt/WCG/logs/content_gateway.out
Use Ctrl+C to terminate the command.

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Security > Proxy user authentication > Multiple realm authentication > Troubleshooting Multiple Realm Authentication