The Bakery Everything CakePHP

Marco,

For a new business office application, I can user REMOTE_USER (from PubCookie) to provide authentication, but I need authorization component.

The inheriting ACL model in 1.2 looks very good, but for this application I need to support membership in multiple groups. Native CakePHP ACLs won't work. So I have been looking around. I looked at the on-line demo of Authake (based on YACCA) and it looks like it behaves in the way that I need. However, it looks like Authake is now abandoned. That might not be so bad except that Authake seems to require a wholesale replacement of /app; if so, that seems like a bad decision and it would stop me from using it.

So, Marco, here I am back looking at the basis for Authake, YACCA, to try to determine whether this could be used in a 1.2 application.

I am a CakePHP newbie, so if you have any general thoughts on this subject (use of YACCA in 1.2) or any thoughts about the future of YACCA, I am interested to know.

Thanks,

Jim
Hi Jim, thank you for your interest, I use my yacca component for every cakephp 1.1 project i do. I have not tested it on 1.2 becouse till now I don't use it. However, I tried the work by Jérôme on authake and i think it is a very good work and I will probably use it on my next projects involved in 1.2. The project is implemented as a plugin and this is a good thing :). I didn't had time to implement yacca as plugin becouse i am always busy. I suggest you to try authake for your projects and since Jérôme has stopped development of authake, I will try to help you if have problems. But first read well the readme included in the authake package and study at cakephp books on-line how plugins work to understand the logic for make your own code modifications.
Ciao
Marco

hey,
I didn't check the whole article, but it looks nice.
I use something very similar The code for storing rules in the database is not given, but it was easy to write my own :-)
Thankyou if you download the sample you find complete management system for users, groups and rules.

http://blog.nospace.net/uploads/authsample.zip

Hello,

I used this component as a base for my site authentication system, and made some changes:

1 - uses a default "anonymous" user, to get and control ACL info for non-logged-in users.

2 - some major component changes. There were a lot of DB calls being made, and I felt that since sessions are persistent (or should be persistent), that the data should be read from the database once, and stored directly in a session var. Then this session var can be called directly. this eliminated much of the back-and-forth DB copy to session var stuff.

Let me know if you want to see the changes that I made - I didn't want to create a new article until you had a look at them (I can send to you if you want)...I hate "forks" - so in an effort to minimize duplication and hopefully if my changes are OK - maybe we could merge them?

let me know your thuoghts. I'am sorry Ian but I have seen the pm only now and effectively I have changed some code from the first release of this article.

Effectively i had noticed the DB Calls and have patched my code.

I have put a downloadable package of YACCA with management system on my blog

http://blog.nospace.net/uploads/authsample.zip