15 Apr
2006
15 Apr
'06
8:44 a.m.
Hi Ramon,
Pier is simply a seaside application, its user model is and should be
unrelated to anything Seaside does. As far as I know, Seaside doesn't
really have any security model, it's just a framework. The config
application has users, which I guess you can call part of Seaside, but
it's really just another app on top of Seaside like Pier. That Pier
offers two security packages, is good, one is simple and written by
the
author of Pier, and one is more complex, especially in the UI, and
offered as an add on by some other author. So, I don't they should be
integrated in any way, they really aren't related. I would however,
like to see more info on how to integrate custom applications meant to
be hosted within Pier, with Piers default Unix Security model. How to
manage and register users from the Pier UI, etc.
OK. The reason why I said security should be integrated is because I
think especially for web applications, security should not be
something to install after, or to make need and decision which kind
of security one want, it should be a fix and deep rooted part of such
a system. like the language E. As an add on, I would afraid that this
could be cracked more easily by some bad guys than if it is
structural part ......
But I think also this discussion is not new. So thanks for
explanation. How can I add users for the Security of Lukas (the unix
ispired)?
Regards
Hans