, false))
{
// do stuff
} else
{
// invalid
}
}
Would be nice to stick this is beforeSave in the model, but you can't
[easily] access the Auth component from the model.
Hope this helps.
On Jan 17, 2008 9:31 AM, dizz [EMAIL PROTECTED] wrote
[easily] access the Auth component from the model.
Hope this helps.
On Jan 17, 2008 9:31 AM, dizz [EMAIL PROTECTED] wrote:
Hello,
I am using the auth component and before my model can validate the
password the auth component already encrypts the password so making it
impossible to use
in the model, but you can't
[easily] access the Auth component from the model.
Hope this helps.
On Jan 17, 2008 9:31 AM, dizz [EMAIL PROTECTED] wrote:
Hello,
I am using the auth component and before my model can validate the
password the auth component already encrypts the password so making
Hi all!
I have the Auth component on every controller in my app, so it makes
sure that the user is logged in before performing any actions. What I
want is if the validated user also has flag that requires them to
change their password, they can't go to any other controller or
perform any
Put the function in beforeFilter of app_controller.
On Jan 16, 11:49 pm, cmbg [EMAIL PROTECTED] wrote:
Hi all!
I have the Auth component on every controller in my app, so it makes
sure that the user is logged in before performing any actions. What I
want is if the validated user also has
Hi,
I am using the Auth component for 1.2 and it is all working fine
except when I go to edit a user I want to have the option to leave the
password field blank and have itleave the password unchanged. Whenever
I do this it rehashes the password using '' as the password. I have
tried using unset
[EMAIL PROTECTED] wrote:
Hi,
I am using the Auth component for 1.2 and it is all working fine
except when I go to edit a user I want to have the option to leave the
password field blank and have itleave the password unchanged. Whenever
I do this it rehashes the password using
PROTECTED] wrote:
you can speciify which fields to update with the 3rd parameter of
Model-save():http://api.cakephp.org/1.2/class_model.html#ebe42ae387be89985b5a35dd4...
On 14 jan, 11:03, Mike Digital Egg [EMAIL PROTECTED] wrote:
Hi,
I am using the Auth component for 1.2 and it is all
/class_model.html#ebe42ae387be89985b5a35dd4...
On 14 jan, 11:03, Mike Digital Egg [EMAIL PROTECTED] wrote:
Hi,
I am using the Auth component for 1.2 and it is all working fine
except when I go to edit a user I want to have the option to leave the
password field blank and have itleave
/1.2/class_model.html#ebe42ae387be89985b5a35dd4...
On 14 jan, 11:03, Mike Digital Egg [EMAIL PROTECTED] wrote:
Hi,
I am using the Auth component for 1.2 and it is all working fine
except when I go to edit a user I want to have the option to leave
the
password field
/class_model.html#ebe42ae387be89985b5a35dd4...
On 14 jan, 11:03, Mike Digital Egg [EMAIL PROTECTED] wrote:
Hi,
I am using the Auth component for 1.2 and it is all working fine
except when I go to edit a user I want to have the option to leave
the
password field blank
/class_model.html#ebe42ae387be89985b5a35dd4.
..
On 14 jan, 11:03, Mike Digital Egg [EMAIL PROTECTED]
wrote:
Hi,
I am using the Auth component for 1.2 and it is all working
fine
except when I go to edit a user I want to have the option to
leave
the
password field
[EMAIL PROTECTED]
wrote:
Hi,
I am using the Auth component for 1.2 and it is all working
fine
except when I go to edit a user I want to have the option to
leave
the
password field blank and have itleave the password unchanged.
Whenever
I do
the Auth component for 1.2 and it is all
working
fine
except when I go to edit a user I want to have the option
to
leave
the
password field blank and have itleave the password
unchanged.
Whenever
I do this it rehashes the password using '' as the
password. I
Auth has done its
business.
Anyone else worked with testAction() and the Auth component?
--~--~-~--~~~---~--~~
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
Gwoo be da man. He pointed me in a much better direction on this.
I defined a CAKE_UNIT_TEST setting in test.php (and bootstrap.php),
used Configure for some test options to decide if the test (when using
testAction()) should bypassSSL, bypassAuth and spoof an Auth User (so
all those functions
Interesting find tonight while playing with the test suite. If you use
testAction() and have the Auth component loading (in the controller or
in your App Controller), and don't explicitly Auth-allow() the action
set in testAction(), then testAction() will fail silenty as it
redirects to the Auth
to use the Auth component. I'm not doing anything fancy with
ACL, but just some basic Controller authorization.
First off, here's my
resource:http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hop...http://www.littlehart.net/atthekeyboard/2007/09/11/a-hopefully-useful
I'm proud to say that after some startling revalations from gwoo, I finally
understand how to use the Auth component. I'm not doing anything fancy with
ACL, but just some basic Controller authorization.
First off, here's my resource:
http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up
Hi,
It was, at one stage, possible to use an empty login function and for the
Auth component to do the rest -- is this still so?
I have this in my app_controller beforeFilter():
$this-Auth-allow('*');
$this-Auth-loginRedirect = '/';
And an empty login() function in my
, 8:16 pm, Dodger [EMAIL PROTECTED] wrote:
Hi,
It was, at one stage, possible to use an empty login function and for the
Auth component to do the rest -- is this still so?
I have this in my app_controller beforeFilter():
$this-Auth-allow('*');
$this-Auth-loginRedirect
not fixed? I would class this as 'critical'.
D.
Dodger wrote:
Hi,
It was, at one stage, possible to use an empty login function and for the
Auth component to do the rest -- is this still so?
I have this in my app_controller beforeFilter():
$this-Auth-allow('*');
$this-Auth
(never tried this), or
any function of your choice ..
What is the rest if no authentication ?
cheers
On Nov 17, 8:16 pm, Dodger [EMAIL PROTECTED] wrote:
Hi,
It was, at one stage, possible to use an empty login function and for the
Auth component to do the rest -- is this still so?
I have
'.
D.
--
View this message in context:
http://www.nabble.com/Auth-componentcan-use-empty-login-function--tf4827793.html#a13813559
Sent from the CakePHP mailing list archive at Nabble.com.
--~--~-~--~~~---~--~~
You received this message because you
Arne,
You don't have to use the Acl component, I was just playing around
with various things and forgot to take it out :) (I'm just picking up
CakePHP myself)
If you don't have $this-Auth available, make sure you're using Auth
in app_controller.php
Sean
On Nov 9, 8:12 pm, Arne-Kolja
Hi Sean,
I got it working now. The only thing that avoided the whole site from
working is the buggy allow() function. You must not put login and
logout into allow() to get auth working.
But thanks anyway, any help is getting one further in learning things,
right? :-)
Arne
On 10 Nov., 17:32,
On Nov 8, 6:33 pm, Arne-Kolja Bachstein [EMAIL PROTECTED] wrote:
But when submitting the form, it redirects me back to the login, pre-
filling the password field with 32 chars (assume it's the md5 hash,
but why?).
That's probably because the authentication is failing, or not being
checked.
Hi Sean,
thanks for pasting it, but there's only one single issue that doesn't
match your config at all: You're using the Acl component... do I
_have_ to use Acl too? I though I could use it without Acl only using
the table data and such, so I did not work with Acl at all.
I did a bit debugging
Hi again,
and sorry, I didnt answer your questions at all.
Yes, I made sure I had configured the right fields and salt is nulled
('') too.
Best regards
Arne
On Nov 9, 4:25 pm, SeanW [EMAIL PROTECTED] wrote:
On Nov 8, 6:33 pm, Arne-Kolja Bachstein [EMAIL PROTECTED] wrote:
But when
with Auth component too (but after the login
step). My code is very similar, except that I'm using in
AppController:
function isAuthorized() {
// This should authorize any controller/action, even if I'm not
logged in, right?
return true;
}
But when I try to access to any controller
I've been having similar problems myself but just haven't taken the
time to look into what's going on.
In my scenario I'm able to login and the Auth component authenticates
me but does not redirect me to the redirectLogin value. After
submitting my information I end up on the login page still
Hi Sean,
it doesn't work the way you posted it, except for me. But I assume it
could also be something with my login view, so could you please post
an example of a working view for this?
Atm I'm doing the following:
// /app/views/users/login.ctp
h1?php __('login'); ?/h1
?php
echo
app_controller with default behaviours, and controllers
can fine tune it.
http://ertw.com/blog/2007/11/04/a-simple-authentication-system-with-cakephp-12-and-auth-component/
It uses controller based authorization (which again can have a global
policy at the app_controller level, and be overridden
I am having troubles with Auth component too (but after the login
step). My code is very similar, except that I'm using in
AppController:
function isAuthorized() {
// This should authorize any controller/action, even if I'm not
logged in, right?
return true;
}
But when I try to access
Hi there,
I tried to implement a simple authentication using the new Auth
component from CakePHP 1.2, but did not succeed. Maybe there's someone
who can give me quick and dirty assistance with this?
My goal is to implement the authentication basics directly into /app/
app_controller.php rather
2007/9/26, Martin Schapendonk [EMAIL PROTECTED]:
Anyone knows what could be happening here?
Let's answer my own email (at least partially).
It is related to the CAKE_SECURITY setting. Changing this setting from
high to medium 'solved' the problem.
The documentation states: CakePHP session IDs
2007/9/27, Martin Schapendonk [EMAIL PROTECTED]:
It is related to the CAKE_SECURITY setting. Changing this setting from
high to medium 'solved' the problem.
In the group archive I read CAKE_SECURITY set to high also checks the
referer, which would explain why it doesn't work with a reverse
Hi,
Not sure if this is offtopic for the list, but I suspect it is (it
seems related to the Auth component).
Using Cake 1.2.0.5427alpha.
I have a Cake setup with a reverse proxy as frontend. This reverse
proxy passes all requests to the cakephp app on the backend webserver
and forwards all
On 8/15/07, Samuel DeVore [EMAIL PROTECTED] wrote:
it's the action you go to when you are denied (at least is how my mind
remembers it)
Which itself should be denied - else the login code in the auth
component does not execute
T
don't need to call isAuthorized() every time you handle a
request, in fact since the Auth component will check to see if it is
Authorized each time it handles a request you are really doubling its
work. If you want to check if a user is logged in you can check the
session variable to see
I searched around trying to find similar problems but I didn't run
into any. If I missed a relevant discussion, pointing me in their
direction would be much obliged.
The first two problems are both with AuthComponent::Allow(). Here's a
snippet from my Users Controller:
function beforeFilter() {
On 8/14/07, rnpg1014 [EMAIL PROTECTED] wrote:
function beforeFilter() {
$this-Auth-allow('login', 'register', 'recover');
login should be a denied action - there is some twisted reasoning for
it but it ultimately makes sense
T
--
it's the action you go to when you are denied (at least is how my mind
remembers it)
On 8/14/07, Dr. Tarique Sani [EMAIL PROTECTED] wrote:
On 8/14/07, rnpg1014 [EMAIL PROTECTED] wrote:
function beforeFilter() {
$this-Auth-allow('login', 'register', 'recover');
login should be
Brians tutorial on Acl and Auth
http://realm3.com/articles/setting_up_users_groups_withacl_and_auth_in_cake_1.2.php
On Aug 2, 11:56 am, luke BAKING barker [EMAIL PROTECTED] wrote:
Hi Gorka - I too am having problem with this issue. I am using the
excellent tutorial by Brian as a starting
On 7/27/07, Gorka [EMAIL PROTECTED] wrote:
I thought AuthComponent handled user login and logout on its own,
validating username/password pairs and thus I saw no reason to use a
validLogin function on the model as you did.
Yes it is supposed to but there is a bug - see this ticket by one o
Hey Tarique, thanks for this reply - perhaps I will try a new nightly
and see if the patch has made it in.
thanks
Luke
On Aug 2, 12:17 pm, Dr. Tarique Sani [EMAIL PROTECTED] wrote:
On 7/27/07, Gorka [EMAIL PROTECTED] wrote:
I thought AuthComponent handled user login and logout on its
On 8/2/07, luke BAKING barker [EMAIL PROTECTED] wrote:
Hey Tarique, thanks for this reply - perhaps I will try a new nightly
and see if the patch has made it in.
If the patch has made it in - the trac is usually updated
In fact there are 4 tickets on auth component which we are awaiting
:
Dunno why but I can't post in the original thread.
original thread= new auth component in cake 1.2
http://groups.google.com/group/cake-php/browse_frm/thread/f2d0143c2e5...
My 2 cents about the new Auth component (Cake 1.2.0.5146alpha)
It stores encrypted passwords in the DB when
but I can't post in the original thread.
original thread= new auth component in cake 1.2
http://groups.google.com/group/cake-php/browse_frm/thread/f2d0143c2e5...
My 2 cents about the new Auth component (Cake 1.2.0.5146alpha)
It stores encrypted passwords in the DB when you add/edit a new
Hi,
I'm trying to use new Auth component. I've got problem with
Auth::validate. I want to use my own validation, not 'actions' or
'objects'. So, as it stands in the comment, in beforeFilter() of my
appController I do:
$this - Auth - validate = null;
However, it doesn't work (maybe I'm wrong
I've tried already, anything changes...
On 5 Lip, 14:59, Chris Hartjes [EMAIL PROTECTED] wrote:
On 7/5/07, Pillow [EMAIL PROTECTED] wrote:
Try $this-Auth-validate = false
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On 7/5/07, Pillow [EMAIL PROTECTED] wrote:
Hi,
I'm trying to use new Auth component. I've got problem with
Auth::validate. I want to use my own validation, not 'actions' or
'objects'. So, as it stands in the comment, in beforeFilter() of my
appController I do:
$this - Auth - validate
Dunno if this can help, but I managed as explained in the following
post:
= http://groups.google.com/group/cake-php/t/871ff4c536bc1e00
Dan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Cake
PHP group.
To post
On 5 Lip, 15:33, danfreak [EMAIL PROTECTED] wrote:
Dunno if this can help, but I managed as explained in the following
post:
=http://groups.google.com/group/cake-php/t/871ff4c536bc1e00
Thanks for this post, it helped mi very much to get familiar with Auth
component :)
However, I don't want
PROTECTED] wrote:
On 5 Lip, 15:33, danfreak [EMAIL PROTECTED] wrote:
Dunno if this can help, but I managed as explained in the following
post:
=http://groups.google.com/group/cake-php/t/871ff4c536bc1e00
Thanks for this post, it helped mi very much to get familiar with Auth
component
On 5 Lip, 19:38, danfreak [EMAIL PROTECTED] wrote:
Try this then in your app_controller:
--
$this-Auth-allow('*');
--
It should work as wildcard
Dunno why but I can't post in the original thread.
original thread= new auth component in cake 1.2
http://groups.google.com/group/cake-php/browse_frm/thread/f2d0143c2e59ce2b/30126ff7024d152c?lnk=gstq=authrnum=2#30126ff7024d152c
My 2 cents about the new Auth component (Cake 1.2.0.5146alpha
Hi,
I was reading the description of the various authentication components/
code that the bakery offers and honestly I am a bit confused.
I don't need groups, I just need that a user can edit his own page but
not other pages. (simple one)
which one should I use?
To use the new Cake 1.2 Auth component I'd like to overload the
isAuthorizied method. This is because I don't or need or want the Auth
component to use ACL. How do I go about doing this?
Thanks,
Aaron
--~--~-~--~~~---~--~~
You received this message because you
coponent+acl in cake
1.2 ?
I guess you could write it ;) I am not sure there is anything out there
yet.
There is indeed an Auth component https://svn.cakephp.org/repo/
trunk/cake/1.2.x.x/cake/libs/controller/components/auth.php in 1.2.
I too was interested in this component
an Auth component https://svn.cakephp.org/repo/
trunk/cake/1.2.x.x/cake/libs/controller/components/auth.php in 1.2.
I too was interested in this component and when asked in IRC,
PhpNut informed me that, we have to write many stuffs and can use the
methods found in the Auth component. So, I'd
PROTECTED] [EMAIL PROTECTED] wrote:
how can i find manual, trytourial about new auth coponent+acl in cake
1.2 ?
I guess you could write it ;) I am not sure there is anything out there
yet.
There is indeed an Auth component https://svn.cakephp.org/repo/
trunk/cake/1.2.x.x/cake
how can i find manual, trytourial about new auth coponent+acl in cake
1.2 ?
--~--~-~--~~~---~--~~
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
On 4/5/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
how can i find manual, trytourial about new auth coponent+acl in cake
1.2 ?
I guess you could write it ;) I am not sure there is anything out there yet.
--~--~-~--~~~---~--~~
You received this message
On Apr 5, 2007, at 2:38 PM, Samuel DeVore wrote:
On 4/5/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
how can i find manual, trytourial about new auth coponent+acl in
cake
1.2 ?
I guess you could write it ;) I am not sure there is anything out
there yet.
And there probably
If your looking for a Auth component, consider othAuth (http://
bakery.cakephp.org/articles/view/99). The documentation is good
(http://bakery.cakephp.org/articles/view/148) and very easy to drop
into your project.
The notes indicate that it will later support CakePHP's own ACL
component
Hi Nate,
Ok - I discovered what I was doing. I was setting
$this-Auth-fields['password'] = 'passwd'; in my app_controller. I
needed to define it in my users_controller.
Now that's working I'm still getting the MD5 problem - Auth seems to
be using plain text passwords, as it doesn't recognise
Yea, unfortunatly I got that today as well (a piss off)
I managed to get it implemented, but still hit a few snags:
Defining $this-Auth-fields = array('password' = 'passwd'); doesn't
seem to work.
Just for testing, I changed the var directly in the component and it
worked, but it seems at the
It's cool y'all, just chill for a bit. Help is on the way... yeah
baby, help is on the way.
digital spaghetti:
If you $this-Auth-fields = array('password' = 'passwd'), that
leaves it without a user name. You need to either do:
$this-Auth-fields['password'] = 'passwd';
- or -
$this-Auth-fields
I got the new AuthComponent going by doing this in UsersController:
function beforeFilter() {
$this-Auth-allow('index', 'register', 'login', 'logout');
}
I'm reading cake/libs/controller/components/auth.php as I go along. My
next step is to figure out how to use $this-Auth-login(). I'm sure I
far but I am ready to take it to the next level.
The first thing I am building into my app is the user system, so users
can log in and get access to specific areas. I've decided to go with
1.2.x.x branch since it has the new Auth component but I've come
across problems already.
In my
it has the new Auth component but I've come
across problems already.
In my AppController class, I have added the Auth component, but now
every page I look at, it's asking me to log in as a user (via /users/
login as the default in Auth), but of course I don't want this on
every page, only pages
801 - 872 of 872 matches
Mail list logo