GroupWise Proxy Redirect Conflicts with NGWNAMESERVER

NGWNAMESERVER and Proxy Redirect share the same Post Office Agent.
Certain users unable to use NGWNAMESERVER and are redirected to the Proxy POA rather than their home POA.

Do not configure the NGWNAMESERVER to reside upon the same POA as one that is set up as a Proxy to redirect through a firewall.

See 'Notes' section.

NGWNAMESERVER is intended to forward errant authentication attempts to the correct home Post Office Agent.  The setting is placed in the server/resource's host information as well as being named in the GroupWise system. 

Proxy redirecting is intended to allow a DMZ POA to redirect users' authentication through a firewall to an internal POA.  This enhances the security of the GroupWise system.  It is possible to have a Proxy POA also exist as the NGWNAMESERVER POA, though this would normally not be the case except in rare cases such as a Citrix environment.

 

Under normal circumstances, any POA would see that they are receiving the 'incorrect' authentication attempt and then automatically redirect the credentials to the correct POA.  In the case where the Proxy redirect and NGWNAMESERVER redirect occur on the same POA, the Proxy not only takes immediate precedence, the redirection also will not move past the next hop, which is where the Proxy sends it.  Currently, this is working as designed.