Re: To use a open source Auth system or not
I guess I just have to go for it and see the results for myself. I just have to tell myself "it's just an auth system" Thanks. On Sep 10, 6:19 am, "Chris Hartjes" <[EMAIL PROTECTED]> wrote: > On 9/10/07, Matt <[EMAIL PROTECTED]> wrote: > > > > > Chris, I found the AuthComponent mentioned in the release for the > > 1.2.0.5427alpha: > >http://bakery.cakephp.org/articles/view/the-last-alpha-cake > > > but to be honest I'm not really that confident using an AuthComponent > > that is in a alpha release. I guess I will just do with what I'm using > > and watch the AuthComponent to see how it turns out. > > We use it at CDC for all our projects, so I guess it's stable enough. :) > > -- > Chris Hartjes > Senior Developer > Cake Development Corporation > > My motto for 2007: "Just build it, damnit!" > > @TheBallpark -http://www.littlehart.net/attheballpark > @TheKeyboard -http://www.littlehart.net/atthekeyboard --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
Sorry, I left out something from that statement: "...until 1.2 goes stable". Yeah, I found it too, but no Auth stuff. Two-Headed Application Authentication in CakePHP 1.2 : http://www.littlehart.net/atthekeyboard/2007/07/28/two-headed-application-authentication-in-cakephp-12/ But, I'm too stupid/lazy to figure it out. I mean, what does the view look like? Up until 30 minutes ago, I didn't know you could use it without the ACL stuff in the background. Stuff like that. I'm not real good at understanding things in units. I work better with a full example where I can see all the parts working together. I'm gonna take one final wack at it. This time I'll go straight to the API and see what I can figure out. But I must warn you, my PHP skills and Framework skills (come to think of it, coding in general lol) are a bit rusty. -- Baz L Web Development 2.0: Web Design, CakePHP, Javascript http://www.WebDevelopment2.com/ On 9/10/07, Dr. Tarique Sani <[EMAIL PROTECTED]> wrote: > > > On 9/10/07, Baz <[EMAIL PROTECTED]> wrote: > > SoI'll be patiently waiting for Chris or someone else to do that > write > > up. Since there's not going to be an official Manual for 1.2, I guess I > have > > to just wait on enterprising bloggers. > > There already is a manual for 1.2 and currently in the same state as > CakePHP v1.2 :) > > Chris has already written about it in the past can't recall the exact > URL but something like two pronged auth or two headed auth > > T > > -- > = > Cheesecake-Photoblog: http://cheesecake-photoblog.org > PHP for E-Biz: http://sanisoft.com > = > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
There you go, that just goes to show that I have no clue what I'm talking about. SoI'll be patiently waiting for Chris or someone else to do that write up. Since there's not going to be an official Manual for 1.2, I guess I have to just wait on enterprising bloggers. -- Baz L Web Development 2.0: Web Design, CakePHP, Javascript http://www.WebDevelopment2.com/ On 9/10/07, Dr. Tarique Sani <[EMAIL PROTECTED]> wrote: > > > On 9/10/07, Baz <[EMAIL PROTECTED]> wrote: > > As far as I understand, the Auth Component is only half of the story. > You > > still have to set up all that ACL stuff before hand. > > No - you can simply use the Auth by writing isAuthorized method in > your controller OR model and setting the appropriate option, this is > typically in your app_controller > > So you write $this->Auth->authorize = 'controller'; or > $this->Auth->authorize = 'model'; > > you can use whatever logic you want in your isAuthorized method > > > > T > > -- > = > Cheesecake-Photoblog: http://cheesecake-photoblog.org > PHP for E-Biz: http://sanisoft.com > = > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
On 9/10/07, Dr. Tarique Sani <[EMAIL PROTECTED]> wrote: > > > Chris has already written about it in the past can't recall the exact > URL but something like two pronged auth or two headed auth > Yeah, I did a small post about it: http://www.littlehart.net/atthekeyboard/2007/07/28/two-headed-application-authentication-in-cakephp-12/ But what I think is needed is a more in-depth posting about how to use Auth. -- Chris Hartjes Senior Developer Cake Development Corporation My motto for 2007: "Just build it, damnit!" @TheBallpark - http://www.littlehart.net/attheballpark @TheKeyboard - http://www.littlehart.net/atthekeyboard --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
On 9/10/07, Matt <[EMAIL PROTECTED]> wrote: > > > Chris, I found the AuthComponent mentioned in the release for the > 1.2.0.5427alpha: > http://bakery.cakephp.org/articles/view/the-last-alpha-cake > > but to be honest I'm not really that confident using an AuthComponent > that is in a alpha release. I guess I will just do with what I'm using > and watch the AuthComponent to see how it turns out. We use it at CDC for all our projects, so I guess it's stable enough. :) -- Chris Hartjes Senior Developer Cake Development Corporation My motto for 2007: "Just build it, damnit!" @TheBallpark - http://www.littlehart.net/attheballpark @TheKeyboard - http://www.littlehart.net/atthekeyboard --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
On 9/10/07, Baz <[EMAIL PROTECTED]> wrote: > SoI'll be patiently waiting for Chris or someone else to do that write > up. Since there's not going to be an official Manual for 1.2, I guess I have > to just wait on enterprising bloggers. There already is a manual for 1.2 and currently in the same state as CakePHP v1.2 :) Chris has already written about it in the past can't recall the exact URL but something like two pronged auth or two headed auth T -- = Cheesecake-Photoblog: http://cheesecake-photoblog.org PHP for E-Biz: http://sanisoft.com = --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
On 9/10/07, Baz <[EMAIL PROTECTED]> wrote: > As far as I understand, the Auth Component is only half of the story. You > still have to set up all that ACL stuff before hand. No - you can simply use the Auth by writing isAuthorized method in your controller OR model and setting the appropriate option, this is typically in your app_controller So you write $this->Auth->authorize = 'controller'; or $this->Auth->authorize = 'model'; you can use whatever logic you want in your isAuthorized method T -- = Cheesecake-Photoblog: http://cheesecake-photoblog.org PHP for E-Biz: http://sanisoft.com = --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
As far as I understand, the Auth Component is only half of the story. You
still have to set up all that ACL stuff before hand.
If you're up to the task:
http://lemoncake.wordpress.com/2007/07/15/using-aclbehavior-in-cakephp-12/
then
http://lemoncake.wordpress.com/2007/07/19/using-authcomponent-and-acl-in-cakephp-12/
I tried going through these, but after an hour of plugging away, I got
discouraged.
I kept thinking, "it's not supposed to be that hard"
Oh well.
On 9/10/07, Matt <[EMAIL PROTECTED]> wrote:
>
>
> Thanks Baz, I've been pulling pieces here and there from obAuth as it
> quite simple but gets the job done as you say. There are few other
> projects I have used for reference as well but I think it mostly has
> come from obAuth.
>
> Chris, I found the AuthComponent mentioned in the release for the
> 1.2.0.5427alpha:
> http://bakery.cakephp.org/articles/view/the-last-alpha-cake
>
> but to be honest I'm not really that confident using an AuthComponent
> that is in a alpha release. I guess I will just do with what I'm using
> and watch the AuthComponent to see how it turns out.
>
> If anyone has used the new AuthComponent and found it to be stable,
> please let me know.
>
> Thanks.
>
> On Sep 9, 9:47 pm, Baz <[EMAIL PROTECTED]> wrote:
> > I think this whole ACL thing isn't what I really need. All this ACO's
> and
> > ARO's and stuff. I mean, there must be a a good use for all of it, but
> I'm
> > beginning to think that it's not for me.
> >
> > Gobblez's got it right. All I need is to either let people in or keep
> them
> > out. I do like the group feature though. The only thing is that it would
> be
> > nice if obAuth could just have an array of allowed actions like array
> > ('edit', 'add', 'delete') etc, instead of having to lock() in every
> action
> > function. Oh well, beggars can't be choosers I guess.
> >
> > Sorry guys, I can see you all shaking your head in disappointment.
> >
> > On 9/9/07, gobblez <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> >
> > > I liked obAuth too. It was simpler than the others seem to be. I took
> > > out the groups feature it had, and made a few small modifications, and
> > > added a few functions that made it easier to compare things (like 2
> > > passwords when registering). I figured why bother having groups/
> > > levels; you're either a user that needs to login, or not. For the
> > > admin features, I just have a separate system/site using the admin
> > > routing (sometimes I name it something weird to keep out URL
> > > guessers); one method I used was putting the password in regex in the
> > > model for that field. Not sure how secure that was though.
> >
> > > On Sep 9, 6:40 pm, Baz <[EMAIL PROTECTED]> wrote:
> > > > obAuth is what I've been using. It's nice, with no thrills. The
> others
> > > are
> > > > just too complicated for what I'm trying to do.
> >
> > > > On 9/9/07, Matt <[EMAIL PROTECTED]> wrote:
> >
> > > > > Thanks for the reply Chris. I'm talking about an authentication
> > > > > system, the ACL part is too simple to bother using someone elses
> > > > > system unless of course this one is simple enough.
> >
> > > > > I've found lots of "add-on" auth components for cake but no
> CakePHP
> > > > > branded authentication component. There's othAuth, dAuth, rbAuth,
> > > > > simpleAuth, obAuthl... but I personally think there is too many
> and
> > > > > when ever I reference them they are always changing or maybe I
> just
> > > > > can't find the one I look at last because they all have the same
> name.
> >
> > > > > I did find the security component which is pretty useful but I
> haven't
> > > > > found an authentication component in the cake libs. Is there
> somewhere
> > > > > I'm not looking?
> >
> > > > > Anyways, a good article or post about this would be invaluable so
> > > > > please let me know if you do.
> >
> > > > > Oh and good luck with your lawn, my apartment didn't come with one
> so
> > > > > atleast you have one.
> >
> > > > > --
> > > > > Matt
> >
> > > > > On Sep 9, 5:55 am, "Chris Hartjes" <[EMAIL PROTECTED]> wrote:
> > > > > > On 9/8/07, Matt <[EMAIL PROTECTED]> wrote:
> >
> > > > > > > I've starting my first cake site, yum cake!
> >
> > > > > > > One of the first decisions I've wondering I've trying to make
> is
> > > to do
> > > > > > > my own auth system or use one of the many being actively
> > > developed. I
> > > > > > > was hoping for some feedback on what others have found what
> has
> > > > > > > worked.
> >
> > > > > > Are you talking about Authentication (where you verify that
> people
> > > > > > have a valid login and password for a site) or Access Control
> (where
> > > > > > you determine if someone has the proper privileges to access a
> > > > > > particular page). People often mix the two together.
> >
> > > > > > If you want to use Authentication and some really simple Access
> > > > > > Control, you can use CakePHP's Auth component. Then, by
> specifying
> > > > > > that you wish to use either a met
Re: To use a open source Auth system or not
Thanks Baz, I've been pulling pieces here and there from obAuth as it
quite simple but gets the job done as you say. There are few other
projects I have used for reference as well but I think it mostly has
come from obAuth.
Chris, I found the AuthComponent mentioned in the release for the
1.2.0.5427alpha:
http://bakery.cakephp.org/articles/view/the-last-alpha-cake
but to be honest I'm not really that confident using an AuthComponent
that is in a alpha release. I guess I will just do with what I'm using
and watch the AuthComponent to see how it turns out.
If anyone has used the new AuthComponent and found it to be stable,
please let me know.
Thanks.
On Sep 9, 9:47 pm, Baz <[EMAIL PROTECTED]> wrote:
> I think this whole ACL thing isn't what I really need. All this ACO's and
> ARO's and stuff. I mean, there must be a a good use for all of it, but I'm
> beginning to think that it's not for me.
>
> Gobblez's got it right. All I need is to either let people in or keep them
> out. I do like the group feature though. The only thing is that it would be
> nice if obAuth could just have an array of allowed actions like array
> ('edit', 'add', 'delete') etc, instead of having to lock() in every action
> function. Oh well, beggars can't be choosers I guess.
>
> Sorry guys, I can see you all shaking your head in disappointment.
>
> On 9/9/07, gobblez <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > I liked obAuth too. It was simpler than the others seem to be. I took
> > out the groups feature it had, and made a few small modifications, and
> > added a few functions that made it easier to compare things (like 2
> > passwords when registering). I figured why bother having groups/
> > levels; you're either a user that needs to login, or not. For the
> > admin features, I just have a separate system/site using the admin
> > routing (sometimes I name it something weird to keep out URL
> > guessers); one method I used was putting the password in regex in the
> > model for that field. Not sure how secure that was though.
>
> > On Sep 9, 6:40 pm, Baz <[EMAIL PROTECTED]> wrote:
> > > obAuth is what I've been using. It's nice, with no thrills. The others
> > are
> > > just too complicated for what I'm trying to do.
>
> > > On 9/9/07, Matt <[EMAIL PROTECTED]> wrote:
>
> > > > Thanks for the reply Chris. I'm talking about an authentication
> > > > system, the ACL part is too simple to bother using someone elses
> > > > system unless of course this one is simple enough.
>
> > > > I've found lots of "add-on" auth components for cake but no CakePHP
> > > > branded authentication component. There's othAuth, dAuth, rbAuth,
> > > > simpleAuth, obAuthl... but I personally think there is too many and
> > > > when ever I reference them they are always changing or maybe I just
> > > > can't find the one I look at last because they all have the same name.
>
> > > > I did find the security component which is pretty useful but I haven't
> > > > found an authentication component in the cake libs. Is there somewhere
> > > > I'm not looking?
>
> > > > Anyways, a good article or post about this would be invaluable so
> > > > please let me know if you do.
>
> > > > Oh and good luck with your lawn, my apartment didn't come with one so
> > > > atleast you have one.
>
> > > > --
> > > > Matt
>
> > > > On Sep 9, 5:55 am, "Chris Hartjes" <[EMAIL PROTECTED]> wrote:
> > > > > On 9/8/07, Matt <[EMAIL PROTECTED]> wrote:
>
> > > > > > I've starting my first cake site, yum cake!
>
> > > > > > One of the first decisions I've wondering I've trying to make is
> > to do
> > > > > > my own auth system or use one of the many being actively
> > developed. I
> > > > > > was hoping for some feedback on what others have found what has
> > > > > > worked.
>
> > > > > Are you talking about Authentication (where you verify that people
> > > > > have a valid login and password for a site) or Access Control (where
> > > > > you determine if someone has the proper privileges to access a
> > > > > particular page). People often mix the two together.
>
> > > > > If you want to use Authentication and some really simple Access
> > > > > Control, you can use CakePHP's Auth component. Then, by specifying
> > > > > that you wish to use either a method in the controller or a method
> > in
> > > > > a model you can do simple access control. I have done this on two
> > > > > different sites now, both CDC projects (one internal, one under
> > > > > development for a client and not ready to show the world yet).
>
> > > > > I was thinking about this while outside putting fertilizer on my
> > lawn
> > > > > in a vain attempt to improve it's scrubby appearance and I think
> > that
> > > > > I need to do a blog post about how to use Auth, collecting all the
> > > > > information I've seen around plus my experience with it as well.
>
> > > > > --
> > > > > Chris Hartjes
> > > > > Senior Developer
> > > > > Cake Development Corporation
>
> > > > > My motto for 2007: "Just build it, d
Re: To use a open source Auth system or not
I think this whole ACL thing isn't what I really need. All this ACO's and
ARO's and stuff. I mean, there must be a a good use for all of it, but I'm
beginning to think that it's not for me.
Gobblez's got it right. All I need is to either let people in or keep them
out. I do like the group feature though. The only thing is that it would be
nice if obAuth could just have an array of allowed actions like array
('edit', 'add', 'delete') etc, instead of having to lock() in every action
function. Oh well, beggars can't be choosers I guess.
Sorry guys, I can see you all shaking your head in disappointment.
On 9/9/07, gobblez <[EMAIL PROTECTED]> wrote:
>
>
> I liked obAuth too. It was simpler than the others seem to be. I took
> out the groups feature it had, and made a few small modifications, and
> added a few functions that made it easier to compare things (like 2
> passwords when registering). I figured why bother having groups/
> levels; you're either a user that needs to login, or not. For the
> admin features, I just have a separate system/site using the admin
> routing (sometimes I name it something weird to keep out URL
> guessers); one method I used was putting the password in regex in the
> model for that field. Not sure how secure that was though.
>
> On Sep 9, 6:40 pm, Baz <[EMAIL PROTECTED]> wrote:
> > obAuth is what I've been using. It's nice, with no thrills. The others
> are
> > just too complicated for what I'm trying to do.
> >
> > On 9/9/07, Matt <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > > Thanks for the reply Chris. I'm talking about an authentication
> > > system, the ACL part is too simple to bother using someone elses
> > > system unless of course this one is simple enough.
> >
> > > I've found lots of "add-on" auth components for cake but no CakePHP
> > > branded authentication component. There's othAuth, dAuth, rbAuth,
> > > simpleAuth, obAuthl... but I personally think there is too many and
> > > when ever I reference them they are always changing or maybe I just
> > > can't find the one I look at last because they all have the same name.
> >
> > > I did find the security component which is pretty useful but I haven't
> > > found an authentication component in the cake libs. Is there somewhere
> > > I'm not looking?
> >
> > > Anyways, a good article or post about this would be invaluable so
> > > please let me know if you do.
> >
> > > Oh and good luck with your lawn, my apartment didn't come with one so
> > > atleast you have one.
> >
> > > --
> > > Matt
> >
> > > On Sep 9, 5:55 am, "Chris Hartjes" <[EMAIL PROTECTED]> wrote:
> > > > On 9/8/07, Matt <[EMAIL PROTECTED]> wrote:
> >
> > > > > I've starting my first cake site, yum cake!
> >
> > > > > One of the first decisions I've wondering I've trying to make is
> to do
> > > > > my own auth system or use one of the many being actively
> developed. I
> > > > > was hoping for some feedback on what others have found what has
> > > > > worked.
> >
> > > > Are you talking about Authentication (where you verify that people
> > > > have a valid login and password for a site) or Access Control (where
> > > > you determine if someone has the proper privileges to access a
> > > > particular page). People often mix the two together.
> >
> > > > If you want to use Authentication and some really simple Access
> > > > Control, you can use CakePHP's Auth component. Then, by specifying
> > > > that you wish to use either a method in the controller or a method
> in
> > > > a model you can do simple access control. I have done this on two
> > > > different sites now, both CDC projects (one internal, one under
> > > > development for a client and not ready to show the world yet).
> >
> > > > I was thinking about this while outside putting fertilizer on my
> lawn
> > > > in a vain attempt to improve it's scrubby appearance and I think
> that
> > > > I need to do a blog post about how to use Auth, collecting all the
> > > > information I've seen around plus my experience with it as well.
> >
> > > > --
> > > > Chris Hartjes
> > > > Senior Developer
> > > > Cake Development Corporation
> >
> > > > My motto for 2007: "Just build it, damnit!"
> >
> > > > @TheBallpark -http://www.littlehart.net/attheballpark
> > > > @TheKeyboard -http://www.littlehart.net/atthekeyboard
>
>
> >
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
I liked obAuth too. It was simpler than the others seem to be. I took out the groups feature it had, and made a few small modifications, and added a few functions that made it easier to compare things (like 2 passwords when registering). I figured why bother having groups/ levels; you're either a user that needs to login, or not. For the admin features, I just have a separate system/site using the admin routing (sometimes I name it something weird to keep out URL guessers); one method I used was putting the password in regex in the model for that field. Not sure how secure that was though. On Sep 9, 6:40 pm, Baz <[EMAIL PROTECTED]> wrote: > obAuth is what I've been using. It's nice, with no thrills. The others are > just too complicated for what I'm trying to do. > > On 9/9/07, Matt <[EMAIL PROTECTED]> wrote: > > > > > Thanks for the reply Chris. I'm talking about an authentication > > system, the ACL part is too simple to bother using someone elses > > system unless of course this one is simple enough. > > > I've found lots of "add-on" auth components for cake but no CakePHP > > branded authentication component. There's othAuth, dAuth, rbAuth, > > simpleAuth, obAuthl... but I personally think there is too many and > > when ever I reference them they are always changing or maybe I just > > can't find the one I look at last because they all have the same name. > > > I did find the security component which is pretty useful but I haven't > > found an authentication component in the cake libs. Is there somewhere > > I'm not looking? > > > Anyways, a good article or post about this would be invaluable so > > please let me know if you do. > > > Oh and good luck with your lawn, my apartment didn't come with one so > > atleast you have one. > > > -- > > Matt > > > On Sep 9, 5:55 am, "Chris Hartjes" <[EMAIL PROTECTED]> wrote: > > > On 9/8/07, Matt <[EMAIL PROTECTED]> wrote: > > > > > I've starting my first cake site, yum cake! > > > > > One of the first decisions I've wondering I've trying to make is to do > > > > my own auth system or use one of the many being actively developed. I > > > > was hoping for some feedback on what others have found what has > > > > worked. > > > > Are you talking about Authentication (where you verify that people > > > have a valid login and password for a site) or Access Control (where > > > you determine if someone has the proper privileges to access a > > > particular page). People often mix the two together. > > > > If you want to use Authentication and some really simple Access > > > Control, you can use CakePHP's Auth component. Then, by specifying > > > that you wish to use either a method in the controller or a method in > > > a model you can do simple access control. I have done this on two > > > different sites now, both CDC projects (one internal, one under > > > development for a client and not ready to show the world yet). > > > > I was thinking about this while outside putting fertilizer on my lawn > > > in a vain attempt to improve it's scrubby appearance and I think that > > > I need to do a blog post about how to use Auth, collecting all the > > > information I've seen around plus my experience with it as well. > > > > -- > > > Chris Hartjes > > > Senior Developer > > > Cake Development Corporation > > > > My motto for 2007: "Just build it, damnit!" > > > > @TheBallpark -http://www.littlehart.net/attheballpark > > > @TheKeyboard -http://www.littlehart.net/atthekeyboard --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
obAuth is what I've been using. It's nice, with no thrills. The others are just too complicated for what I'm trying to do. On 9/9/07, Matt <[EMAIL PROTECTED]> wrote: > > > Thanks for the reply Chris. I'm talking about an authentication > system, the ACL part is too simple to bother using someone elses > system unless of course this one is simple enough. > > I've found lots of "add-on" auth components for cake but no CakePHP > branded authentication component. There's othAuth, dAuth, rbAuth, > simpleAuth, obAuthl... but I personally think there is too many and > when ever I reference them they are always changing or maybe I just > can't find the one I look at last because they all have the same name. > > I did find the security component which is pretty useful but I haven't > found an authentication component in the cake libs. Is there somewhere > I'm not looking? > > Anyways, a good article or post about this would be invaluable so > please let me know if you do. > > Oh and good luck with your lawn, my apartment didn't come with one so > atleast you have one. > > -- > Matt > > On Sep 9, 5:55 am, "Chris Hartjes" <[EMAIL PROTECTED]> wrote: > > On 9/8/07, Matt <[EMAIL PROTECTED]> wrote: > > > > > > > > > I've starting my first cake site, yum cake! > > > > > One of the first decisions I've wondering I've trying to make is to do > > > my own auth system or use one of the many being actively developed. I > > > was hoping for some feedback on what others have found what has > > > worked. > > > > Are you talking about Authentication (where you verify that people > > have a valid login and password for a site) or Access Control (where > > you determine if someone has the proper privileges to access a > > particular page). People often mix the two together. > > > > If you want to use Authentication and some really simple Access > > Control, you can use CakePHP's Auth component. Then, by specifying > > that you wish to use either a method in the controller or a method in > > a model you can do simple access control. I have done this on two > > different sites now, both CDC projects (one internal, one under > > development for a client and not ready to show the world yet). > > > > I was thinking about this while outside putting fertilizer on my lawn > > in a vain attempt to improve it's scrubby appearance and I think that > > I need to do a blog post about how to use Auth, collecting all the > > information I've seen around plus my experience with it as well. > > > > -- > > Chris Hartjes > > Senior Developer > > Cake Development Corporation > > > > My motto for 2007: "Just build it, damnit!" > > > > @TheBallpark -http://www.littlehart.net/attheballpark > > @TheKeyboard -http://www.littlehart.net/atthekeyboard > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
Thanks for the reply Chris. I'm talking about an authentication system, the ACL part is too simple to bother using someone elses system unless of course this one is simple enough. I've found lots of "add-on" auth components for cake but no CakePHP branded authentication component. There's othAuth, dAuth, rbAuth, simpleAuth, obAuthl... but I personally think there is too many and when ever I reference them they are always changing or maybe I just can't find the one I look at last because they all have the same name. I did find the security component which is pretty useful but I haven't found an authentication component in the cake libs. Is there somewhere I'm not looking? Anyways, a good article or post about this would be invaluable so please let me know if you do. Oh and good luck with your lawn, my apartment didn't come with one so atleast you have one. -- Matt On Sep 9, 5:55 am, "Chris Hartjes" <[EMAIL PROTECTED]> wrote: > On 9/8/07, Matt <[EMAIL PROTECTED]> wrote: > > > > > I've starting my first cake site, yum cake! > > > One of the first decisions I've wondering I've trying to make is to do > > my own auth system or use one of the many being actively developed. I > > was hoping for some feedback on what others have found what has > > worked. > > Are you talking about Authentication (where you verify that people > have a valid login and password for a site) or Access Control (where > you determine if someone has the proper privileges to access a > particular page). People often mix the two together. > > If you want to use Authentication and some really simple Access > Control, you can use CakePHP's Auth component. Then, by specifying > that you wish to use either a method in the controller or a method in > a model you can do simple access control. I have done this on two > different sites now, both CDC projects (one internal, one under > development for a client and not ready to show the world yet). > > I was thinking about this while outside putting fertilizer on my lawn > in a vain attempt to improve it's scrubby appearance and I think that > I need to do a blog post about how to use Auth, collecting all the > information I've seen around plus my experience with it as well. > > -- > Chris Hartjes > Senior Developer > Cake Development Corporation > > My motto for 2007: "Just build it, damnit!" > > @TheBallpark -http://www.littlehart.net/attheballpark > @TheKeyboard -http://www.littlehart.net/atthekeyboard --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
Oh yeah, That would be awesome, lol. I'm sorry, but I'm still not getting it. I'm gonna go over what I got today and give it one more shot. If I get it working I'll let you know where I had my hiccups so you can include those in what you do. -- Baz L Web Development 2.0: Web Design, CakePHP, Javascript http://www.WebDevelopment2.com/ On 9/9/07, Chris Hartjes <[EMAIL PROTECTED]> wrote: > > > On 9/8/07, Matt <[EMAIL PROTECTED]> wrote: > > > > I've starting my first cake site, yum cake! > > > > One of the first decisions I've wondering I've trying to make is to do > > my own auth system or use one of the many being actively developed. I > > was hoping for some feedback on what others have found what has > > worked. > > Are you talking about Authentication (where you verify that people > have a valid login and password for a site) or Access Control (where > you determine if someone has the proper privileges to access a > particular page). People often mix the two together. > > If you want to use Authentication and some really simple Access > Control, you can use CakePHP's Auth component. Then, by specifying > that you wish to use either a method in the controller or a method in > a model you can do simple access control. I have done this on two > different sites now, both CDC projects (one internal, one under > development for a client and not ready to show the world yet). > > I was thinking about this while outside putting fertilizer on my lawn > in a vain attempt to improve it's scrubby appearance and I think that > I need to do a blog post about how to use Auth, collecting all the > information I've seen around plus my experience with it as well. > > -- > Chris Hartjes > Senior Developer > Cake Development Corporation > > My motto for 2007: "Just build it, damnit!" > > @TheBallpark - http://www.littlehart.net/attheballpark > @TheKeyboard - http://www.littlehart.net/atthekeyboard > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: To use a open source Auth system or not
On 9/8/07, Matt <[EMAIL PROTECTED]> wrote: > > I've starting my first cake site, yum cake! > > One of the first decisions I've wondering I've trying to make is to do > my own auth system or use one of the many being actively developed. I > was hoping for some feedback on what others have found what has > worked. Are you talking about Authentication (where you verify that people have a valid login and password for a site) or Access Control (where you determine if someone has the proper privileges to access a particular page). People often mix the two together. If you want to use Authentication and some really simple Access Control, you can use CakePHP's Auth component. Then, by specifying that you wish to use either a method in the controller or a method in a model you can do simple access control. I have done this on two different sites now, both CDC projects (one internal, one under development for a client and not ready to show the world yet). I was thinking about this while outside putting fertilizer on my lawn in a vain attempt to improve it's scrubby appearance and I think that I need to do a blog post about how to use Auth, collecting all the information I've seen around plus my experience with it as well. -- Chris Hartjes Senior Developer Cake Development Corporation My motto for 2007: "Just build it, damnit!" @TheBallpark - http://www.littlehart.net/attheballpark @TheKeyboard - http://www.littlehart.net/atthekeyboard --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
