Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 39135 invoked by uid 500); 10 Aug 2001 13:51:51 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 39118 invoked from network); 10 Aug 2001 13:51:51 -0000 Message-ID: <006601c121a3$a3cc5df0$4a1685c6@sashimi> From: "Bill Stoddard" To: References: <088b01c1219f$44e660f0$0102a8c0@ebprovider.com> Subject: Re: writing a soap/web services authorization module over Apache Date: Fri, 10 Aug 2001 09:51:59 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Status: O X-Status: X-Keywords: X-UID: 414 Sounds interesting but I have no time at all to investigate. Thumbing through the latest DDJ last night and found an article on SOAP::Lite for Perl. Seems you can use it with Apache and mod_perl. http://www.soaplite.com/ FWIW... Bill ----- Original Message ----- From: "Tarun Upadhyay" To: Sent: Friday, August 10, 2001 9:20 AM Subject: writing a soap/web services authorization module over Apache > Hi, > > I am writing an apache module to authorize user access to particular soap > services or methods. > We are calling it mod_soap_auth and it will be hosted at > http://soapuddi.sourceforge.net > > Our basic design allows the use of another module (say mod_auth or > something else) to authenticate users but through an "access file", we > authorize users to connect to particular web-service or its methods. > > We want the user to be able to authorize users at either top, service or > method level. I want to ask how should such a file (and corresponding access > policies) be structured. The requirements are: > a) the structure stays consistent with current apache configuration files > and .htaccess > b) should be xml > c) should be as intuitive to user as possible and efficient to parse for > large number of users or services. > > What does the group think about the file structure and the whole idea in > general? > Am I missing something or is this the correct way? Or am I completely > barking in the dark and this does not make any sense to anybody here? > > ================ > With Warm Regards > Tarun Upadhyay > http://www.tarunupadhyay.com >