[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bricolage-devel
Subject:    Re: Bric Auth
From:       Matt Rolf <rolfm () denison ! edu>
Date:       2008-10-20 19:27:14
Message-ID: 9D1D1BD1-ADDF-49E8-BC7A-4D9031B09168 () denison ! edu
[Download RAW message or body]

BTW David, I was planning to develop this against trunk.

-Matt

On Oct 20, 2008, at 2:03 PM, Beaudet, David wrote:

>
> OK, never mind about falling back.  I see that AUTH_ENGINES is a space
> delimited list that is designed to try each engine in order... so FTP
> would be fine so long as Internal is not removed from the AUTH_ENGINES
> list and the password for FTP is synced up with the Bricolage DB.
>
> Only drawback here is that the credentials for the FTP server are not
> centralized.
>
> -----Original Message-----
> From: Beaudet, David [mailto:D-Beaudet@NGA.GOV]
> Sent: Monday, October 20, 2008 1:56 PM
> To: devel@lists.bricolage.cc
> Subject: Bric Auth
>
>
>
> There was some discussion last week on the list about modifying the  
> way
> authentication works to enable Internal via Bric DB lookup v.s.  
> external
> (i.e. Apache) authentication via other methods.
>
>
>
> What about the built-in FTP server?  That doesn't exactly benefit from
> REMOTE_USER.   Since it's probably a template developer-centric  
> feature,
> could we just force Internal authentication always for that feature or
> does anyone have a better idea?
>
>
>
>
>

[prev in list] [next in list] [prev in thread] [next in thread]