CFML Session settings affecting DW Login Behaviour?

[eapostol]

Hi everyone - I think I am going a little stir crazy. I've been using
Dreamweaver / Ultradev since DW1/UD1/Drumbeat and have used the login
authentication behavior on many occasions, with no problems, until now... The
problem is this: I am using the CFMX 6.1 both locally and on the production
server. Dreamweaver has a site view set up with the CFMX server model locally.
The database table containing the usernames and passwords is in an MS Access dB
(for now). I used DW to create the login authentication behavior (Insert >
Application Objects > Authentication > Log In User). The login page was
created with a form...the main page has the authenticate user behaviour. The
main page has a logout link that logs out the user. The main page redirects the
user to a fail page if they have not logged in. Everything works fine when I
surf to these pages...locally. These pages also work when I surf to them on
another machine within our network. However - posting the pages onto the
production server, with (supposedly) the exact same settings on the CFMX Server
as our local dev servers , then surfing to them, always causes the user to go
to the failure page. No pages were altered after instituting the behaviouir.
Just the raw CFMX code. Upon intial debugging, I discovered that the database
comparison code actually works (alerting that yes there is a match, or no there
is not a match) so my focus is on the session var settings... Again, none of
the code was altered, these lines look innocent enough. So what am I missing?
Why would the login behaviour always go to the failure page when these pages
are visited from a production server? Is there some CFMX Server settings I need
to adjust? regards

<cflock scope="Session" timeout="30" type="Exclusive">
<cfset Session.MM_Username=FORM.ud_username>
<cfset Session.MM_UserAuthorization=MM_rsUser.UserLevel[1]>
...ETC...

[Paul Whitham TMM]

I have run into exactly the same problem before and it is a PITA.

Firstly I would confirm that sessions are being allowed on the server by
using a test page to set a session and then try to read it on the following
page. If this errors then you may need to contact the admin of the server.

I ended up using cookies rather than sessions to resolve the problem

--
Regards

Paul Whitham
Macromedia Certified Professional for Dreamweaver MX2004
Valleybiz Internet Design
[url]www.valleybiz.net[/url]

Team Macromedia Volunteer for Ultradev/Dreamweaver MX
[url]www.macromedia.com/support/forums/team_macromedia[/url]

"eapostol" <webforumsuser@macromedia.com> wrote in message
news:d1comh$md5$1@forums.macromedia.com...

> Hi everyone - I think I am going a little stir crazy. I've been using
> Dreamweaver / Ultradev since DW1/UD1/Drumbeat and have used the login
> authentication behavior on many occasions, with no problems, until now...

The

> problem is this: I am using the CFMX 6.1 both locally and on the

production

> server. Dreamweaver has a site view set up with the CFMX server model

locally.

> The database table containing the usernames and passwords is in an MS

Access dB

> (for now). I used DW to create the login authentication behavior (Insert
>
> Application Objects > Authentication > Log In User). The login page was
> created with a form...the main page has the authenticate user behaviour.

The

> main page has a logout link that logs out the user. The main page

redirects the

> user to a fail page if they have not logged in. Everything works fine

when I

> surf to these pages...locally. These pages also work when I surf to them

on

> another machine within our network. However - posting the pages onto the
> production server, with (supposedly) the exact same settings on the CFMX

Server

> as our local dev servers , then surfing to them, always causes the user

to go

> to the failure page. No pages were altered after instituting the

behaviouir.

> Just the raw CFMX code. Upon intial debugging, I discovered that the

database

> comparison code actually works (alerting that yes there is a match, or no

there

> is not a match) so my focus is on the session var settings... Again, none

of

> the code was altered, these lines look innocent enough. So what am I

missing?

> Why would the login behaviour always go to the failure page when these

pages

> are visited from a production server? Is there some CFMX Server settings I

need

> to adjust? regards
>
> <cflock scope="Session" timeout="30" type="Exclusive">
> <cfset Session.MM_Username=FORM.ud_username>
> <cfset Session.MM_UserAuthorization=MM_rsUser.UserLevel[1]>
> ...ETC...
>

[Massimo Foti]

"eapostol" <webforumsuser@macromedia.com> wrote in message
news:d1comh$md5$1@forums.macromedia.com...

> ? Is there some CFMX Server settings I need
> to adjust? regards

Check this:

[url]http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_16564[/url]


--
----------------------------
Massimo Foti
DW tools: [url]http://www.massimocorner.com[/url]
CF tools: [url]http://www.olimpo.ch/tmt/[/url]
----------------------------