On Mon, Aug 31, 2009 at 10:11 AM, Chris Lewis wrote:
>
> Thanks David,
>
> I hacked together some auth/restriction code built on JPA, based on the
> ProtoUser source (pretty simple). I've said before that I didn't really
> like Mapper (haven't played with Record), but my real concern, as seen
> in
Thanks David,
I hacked together some auth/restriction code built on JPA, based on the
ProtoUser source (pretty simple). I've said before that I didn't really
like Mapper (haven't played with Record), but my real concern, as seen
in other threads, is a that snippets are explicitly coupled with
On Sun, Aug 30, 2009 at 8:21 AM, Chris Lewis wrote:
>
> Thanks David,
>
> That does help, yes. My first toy app, which I wrote for a company demo,
> used lift 1.0 and mapper. I dug into the MegaProtoUser source and
> remember how it worked (providing its own site menu configurations with
> access
Thanks David,
That does help, yes. My first toy app, which I wrote for a company demo,
used lift 1.0 and mapper. I dug into the MegaProtoUser source and
remember how it worked (providing its own site menu configurations with
access control there). Role-based restrictions could be done much the
A your talking about access control? That is something different. See
DPP's response about that as his answer I believe is what you want.
Regarding the JPA example I'll look at that - there have been some breaking
changes in trunk recently so its likely that they have not been updated.
Chee
On Thu, Aug 27, 2009 at 6:42 PM, Chris Lewis wrote:
>
> Lift users,
>
> I'm curious what you all are using for user access control (Mapper users
> excluded). I'm seriously evaluating lift for a project that will use
> JPA. My full time job uses Spring Security, which while nice in that it
> stays
Tim,
No, just looking around at a higher level. Back to what I like about
spring security, it stays entirely out of application code's way (as
does the protouser stuff). I will look at those auth examples, and I
will poke through (Mega)ProtoUser source (I'm more accustomed to having
an applic
Chris,
Are you thinking along the lines of JAAS or similar? As Marius said,
we currently don't have a defined way of doing general purpose
authentication within Lift apps
Cheers, Tim
Sent from my iPhone
On 28 Aug 2009, at 08:14, "marius d." wrote:
>
> I'm not sure you HTTP authentication
I'm not sure you HTTP authentication is what your looking for. Lift
has support for both BASIC and DIGEST authentication models
(irrespective of any persistence technology) and you can grant access
based on Roles defined as a hierarchical structure.
See /examples/http-authentication application.
