Just to add to what Dalius has said...
> > a) the author or authkit is never aroundI am occasionally ;-)
> > b) authkit is way over complicatedAgreed, but authentication and authorisation *is* complicated and
there are lots of different use cases.
> > c) autukit sucks in other ways???
> > d) all of the above.
> This is unfortunately very true. I looked at AuthKit for possibleAuthKit tries to be a flexible basis for your own system. Sometimes it
> inclusion in a project of mine, but it's complicated in areas it
> doesn't need to be, very basic in other areas, and not very flexible.
> In the end I wrote my own authorisation and authentication system.
is easier to create your own system than to base it on AuthKit, I
don't have a problem with that.
> These are the things I wanted in my auth+auth system:AuthKit can help with all these things apart from Customisable table
> - Customisable table names
> - Users, Roles and Permissions
> - Hide/show menu items pulled from the DB, based on permissions
> - Enable/disable links, based on permissions
> - Hide/show sections of pages, based on permissions
> - User access to pages/methods, based on permissions
> - Fairly simple access checking
names but it doesn't provide a GUI admin system which seems to be what
you are after?
> I haven't gotten the "access to pages/methods" going yet (not 100%That's not really true is it? Have you seen this:
> sure how to implement it yet), but I have the rest of the stuff
> Some of the reasons why I couldn't use AuthKit:
There are permissions for all sorts of things to do with roles,
% if authorized(RemoteUser()):
Good luck with your implementation anyway.
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.