[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference gyro::internet_toolss

Title:Internet Tools
Notice:Report ALL NETSCAPE Problems directly to [email protected].rnet? Read note 448.L for beginner information.
Moderator:teco.mro.dec.com::tecotoo.mro.dec.com::mayer
Created:Fri Jun 25 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4714
Total number of notes:40609

4491.0. "Use of Access Control Lists for Secure Access to WEBPages" by JALOPY::CUTLER () Fri Feb 21 1997 10:31

I have an OpenVMS customer who would like to provide secure access to webpages
based on OpenVMS User Authentication and ACL's. Has this been done before, can
this be done, if so, how?

Rick C.
Ford Sales Support
Detroit, Michigan
 
T.RTitleUserPersonal
Name
DateLines
4491.1No Direct Link From Remote User To Local Profile...xdelta.zko.dec.com::HOFFMANSteve, OpenVMS EngineeringFri Feb 21 1997 14:1020
:I have an OpenVMS customer who would like to provide secure access to webpages
:based on OpenVMS User Authentication and ACL's. Has this been done before, can
:this be done, if so, how?

   ACLs are a host-local construct, and -- without having some sort of 
   external authentication of the user, information that could be translated
   into OpenVMS attributes `visible' to the ACL processing -- is not directly
   applicable to webservers. 

   The ACL would differentiate by the username of the webserver, or the
   webserver would need to impersonate the target user (or add on the
   necessary identifiers), or the CGI would need to impersonate the
   target user (or add on the necessary identifiers).

   External authentication is the interesting part of all this...

   You could quite conceivably have webservers running under different
   usernames, etc.

4491.2Purveyor and Custom Auth DLLSTAR::WALDSat Feb 22 1997 17:5214
    The Purveyor webserver for OpenVMS allows for a user-supplied
    authentication DLL which will replace the normal basic authentication
    mechanism.  Included with the Purveyor distribution is a sample
    authentication DLL that validates users using the SYSUAF.   This would
    allow you to restrict access to web pages based on the VMS username. 
    
    Determining what pages a given user has access to still has to be done
    using the Purveyor's access controls, however, so there is no way to
    restrict access to pages based on OpenVMS ACLs.  The user account uder which 
    the Purveyor worker processes run must have access to all of the pages it serves 
    out.
    
    Hans.