Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 82798 invoked from network); 16 Oct 2003 23:00:49 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 16 Oct 2003 23:00:49 -0000 Received: (qmail 11848 invoked by uid 500); 16 Oct 2003 23:00:19 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 11836 invoked by uid 500); 16 Oct 2003 23:00:18 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 11816 invoked from network); 16 Oct 2003 23:00:18 -0000 Received: from unknown (HELO out2.smtp.messagingengine.com) (66.111.4.26) by daedalus.apache.org with SMTP; 16 Oct 2003 23:00:18 -0000 Received: from mail.messagingengine.com (localhost [127.0.0.1]) by localhost.localdomain (Postfix) with ESMTP id 54F002F9B3E for ; Thu, 16 Oct 2003 18:59:55 -0400 (EDT) Received: from 10.202.2.150 ([10.202.2.150] helo=mail.messagingengine.com) by messagingengine.com with SMTP; Thu, 16 Oct 2003 18:59:55 -0400 X-Epoch: 1066345195 X-Sasl-enc: 41810J8yYinv7Y5KIcE6DQ Received: from bronfman504 (Toronto-HSE-ppp3775128.sympatico.ca [67.68.201.217]) by mail.messagingengine.com (Postfix) with ESMTP id 0EC782F858F for ; Thu, 16 Oct 2003 18:59:54 -0400 (EDT) Date: Thu, 16 Oct 2003 19:04:59 -0400 (Eastern Daylight Time) From: Joshua Slive To: users@httpd.apache.org In-Reply-To: Message-ID: References: X-X-Sender: slive@fastmail.fm@mail.messagingengine.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: Re: [users@httpd] password aging X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Thu, 16 Oct 2003, MICHAEL PATTERSON wrote: > I'm not real familiar with apache, but we have a request to age apache > logins and have them expire after 90 days. I have looked at the generic > htaccess process. Some folks have pointed me at mod_ldap, mod_auth_dbm, > etc., but I don't see aging possibilities there either. Any help would be > appreciated. Thanks. In general, apache and its modules simply verify a password against a database. Management of that database (adding users, changing passwords, etc) must be setup independently. The same would go for password aging. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org