We have DNN 5.5 installed as an extranet application in our DMZ.  There are some other applications within our intranet that need to be accessed over the Internet by customers.  We would like to avoid requiring the customers to use a VPN client.  Our hope is to use a reverse proxy installed in our DMZ to support this.  At this time we have the Squid open source reverse proxy installed and it is working to provide access to the intranet applications.

What we would very much like is to have our DNN portal act as the authentication provider for the reverse proxy.  I.E.: until a user successfully logs into our DNN site, they will be unable to access the other applications through the reverse proxy.  The login process within DNN would provide the user authentication for the proxy.  I am trying to figure out what the best way to implement this authentication is.  Right now, the best route I see is to modify the authentication software within Squid to perform a check to ensure that a user is logged into DNN before allowing access to the other servers.  I'm not sure how to do this, and it occurs to me that others must have implemented  similar system.  I would appreciate and advice / pointers for anyone using DNN and a reverse proxy and a single-point login such as the DNN login.