[daisy] daisywiki prefix configuration out of DAISY_HOME

[Tom Brusselle]

If your new (persistent) authentication scheme would allow the safe 
passage of authentication data without having to purchase a separate 
certificate for every domain, then that would indeed solve the problem.

My first thought to implement persistent login would be via a cached 
cookie.  And in this case i don't think persistent login has a lot of 
overlap with secure transmission of (first time) login credentials. 
You'd have persistent login but not necessarily secure login if you 
don't do it over https.

To solve the 2 problems at once, i think you'd have to implement your 
scheme by setting up a seperate authentication service.  That service 
could then be used by different daisies and only require 1 certificate. 
   This seems a lot more complicated.

You might be planning on implementing this anyway, and i if you do, it 
would indeed allow for a cleaner solution to our problem.  But right 
now, bypassing the problem by running each daisy on 2 different 
locations seems a lot simpler than implementing this whole new 
authentication scheme.

Apart from the authentication problem, i can imagine that having the 
flexibility to run one daisy-wiki at different locations could be nice 
for other people or other situations.  But it isn't really a blocker 
today, because it is already possible by editing the sitemap.xmap or 
running 2 different daisywikis.  (although both have a disadvantage as i 
pointed out in a previous mail)  But i guess daisy is already pretty 
flexible, so i won't complain :)

regards,

Tom

Steven Noels wrote:
> On 19 Mar 2008, at 12:15, Tom Brusselle wrote:
> 
>> The reason we chose for this setup was to avoid editor logins on the 
>> website over plain http.
> 
> Once this issue would be solved, would this setup still be desired? The 
> subtle difference between bypassing and solving a problem. ;-)
> 
> For conversational matters with a funding customer, Karel has set up a 
> wiki discussion area, and there's mentionings about a persistent login 
> feature:
> 
> http://cocoondev.org/wiki/g5/580-cd.html
> 
> We could discuss if the safe (https) passage of authentication data also 
> becomes a requirement for this new feature. Agreed, we then also should 
> think about the certificate cost problem for mass-hosted Daisies.
> 
> </Steven>
> --Steven Noels                            http://outerthought.org/
> Outerthought                              Open Source Java & XML
> stevenn at outerthought.org              Makers of the Daisy CMS
> _______________________________________________
> daisy community mailing list
> Professional Daisy support: 
> http://outerthought.org/en/services/daisy/support.html
> mail to: daisy at lists.cocoondev.org
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
> 

 **** DISCLAIMER ****
 http://www.schaubroeck.be/maildisclaimer.htm