[Help-smalltalk] HTTP Authentication in Swazoo (was Seaside, some questions...)

[Janko Mivšek]

Hi guys,

Swazoo 1 has a workable HTTP Authentication-Basic implemented and used
in practice, while Digest one was almost implemented. Due to lack of
time it was not ported to a new request framework in Swazoo 2, but it
shouldn't be hard to do now.

If someone is interested, you can count on all my support, we also need
it in Aida/Web to put back to live its WebDAV support, which needs HTTP
Authentication too.

Best regards
Janko

Paolo Bonzini pravi:

>> - How do you secure the config-site of seaside with - at minimum - a
>> user/password? (I tried a load into squeak, and it asked me for a
>> user/password combination, but where is it saved, that I could set it in
>> gst "by hand"? Or is it because of the difference between swazoo and
>> comanche. And if so, how do you workaround it.)
> 
> It looks like this part is unimplemented in Swazoo, OTOH it seems pretty
> easy to do (the HTTPAuthenticationChallenge class is missing).  (swazoo
> list CCed).
> 
> I think what is often done, is to firewall Swazoo, and instead use
> Apache as a proxy server.  You then configure Apache to block
> /seaside/config and to use it, you access Swazoo directly (because of
> the firewall, that would be possible only within some kind of DMZ).
> 
>  > - Do you hide the /seaside/ path somehow for the user?
> 
> If you want this, you have to make the root entry point the
> WAApplication instead of using a WADispatcher as Seaside does by default.
> 
>> - Do you really need the halos for development? (And if so, how do you
>> activate them. I know the entry about seaside on
>> http://smalltalk.gnu.org, but I couldn't add something like
>> WAToolConfiguration to the configuration of my application. My page
>> looked like: http://up.picr.de/2368288.jpg
> 
> click Override in decoration classes. They are not necessary, but very
> useful.
> 
> Paolo


-- 
Janko Mivšek
AIDA/Web
Smalltalk Web Application Server
http://www.aidaweb.si