Re^2: [Catalyst] authenticate called with nonexistant realm: 'default'

I am using version 0.10023.
I have tested with the pre version 0.10008 of the configuration, just to be sure, but no luck.
I have also tried to put the configuration in the same file as my login function (don't know if that can make any difference?), but it still doesn't seem to find the realm 'default', or any other I might put in.

Comment on Re^2: [Catalyst] authenticate called with nonexistant realm: 'default'

Replies are listed 'Best First'.
Re^3: [Catalyst] authenticate called with nonexistant realm: 'default' by Your Mother (Archbishop) on Apr 16, 2014 at 17:36 UTC
I messed around with this a little bit more last night but had exactly the same experience you did. There seems to be something wrong with the docs or a newish bug. I have used the auth package in lots of places without problems before so it's probably something simple that's missing/wrong. I won't have time to look at this today but if no one else chimes in I will try again when I can.	[reply]
Re^4: [Catalyst] authenticate called with nonexistant realm: 'default' by mcso (Novice) on Apr 24, 2014 at 06:56 UTC
I have finally found my mistake, and damn I feel stupid now... In the configuration of my default realm, I have a `credentials` where it should have been `credential` ... the documentation also uses the singular form. I noticed it by going through Catalyst/Plugin/Authentication.pl, looking at the initialization code (_authentication_initialize()). For each found possible realm, it looks for either `credential` or `class` exists. As bonus info, it looks like the module still supports putting all of your realms inside a `realms` hash. Thank you for your time, I will go back and bash my head against the wall..	[reply] [d/l] [select]
Re^5: [Catalyst] authenticate called with nonexistant realm: 'default' by Anonymous Monk on Apr 24, 2014 at 07:41 UTC
I have finally found my mistake, and damn I feel stupid now... In the configuration of my default realm, I have a credentials where it should have been credential ... t Please don't feel stupid -- this is a bug in the module, you should report it Practically everybody gets tripped up by this code configuration via YAML file because it doesn't catch typos ... humans having to catch typos is stupid :) the module should do it	[reply]