Re: How to do forms authentication with cookieless=UseUri?
- From: bruce barker <brucebarker@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 25 Jan 2008 15:22:01 -0800
you are confusing session and authentication. they are unrelated.
forms authentication create a login ticket and stores it in a cookie or the
url. session also creates a session ticket and stores it in a cookie or the
url. they can both use cookies, uri or be configured differently.
storing the login ticket in session just reduces the number of tickets sent
to the client.
cookie is slighty more secure (if you use https) because its not in the url.
the most secure is to not use forms authentication but rather a secure one
like kerberos or basic over https. then you store the login in the session,
and on every session fetch, check the the login matches the authenticated
user (thus preventing session hijacks)
-- bruce (sqlwork.com)
"gnewsgroup" wrote:
On Jan 25, 12:11 pm, bruce barker.
<brucebar...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
no codebehind changes usually are required except with redirects. you should
be using relative or "~" urls. links can also be a problem.
this is because cookieless changes the url to have a login ticket. say your
site is:
http://localhost/mysite/default.aspx
in cookieless it becomes
http://localhost/mysite/<login ticket>/default.aspx
if your redirect does not include the login ticket, then the user is logged
out. you can use cookiesless sessions, and the session ticket is appended to
the authenication ticket.
-- bruce (sqlwork.com)
Thanks. Our client is cookie-phobic, even if it is encrypted and only
contains the username (which is public info anyway) and some
timestamp. So, I thought maybe I can do cookieless.
But, after reading some articles online, I find that cookieless
session may even be worse because the session id directly displays
itself in the URL (at least it is much easier to steal).
So, I guess my question becomes this:
Given that cookies are not allowed, what's the most secure way of
doing authentication? I don't want to go for the classic-asp approach
of checking the session value of USERNAME (for example) on each and
every single page. I am using asp.net 2.0.
- Follow-Ups:
- Re: How to do forms authentication with cookieless=UseUri?
- From: gnewsgroup
- Re: How to do forms authentication with cookieless=UseUri?
- References:
- How to do forms authentication with cookieless=UseUri?
- From: gnewsgroup
- Re: How to do forms authentication with cookieless=UseUri?
- From: gnewsgroup
- How to do forms authentication with cookieless=UseUri?
- Prev by Date: Re: odbc connection
- Next by Date: Publishing My Website II
- Previous by thread: Re: How to do forms authentication with cookieless=UseUri?
- Next by thread: Re: How to do forms authentication with cookieless=UseUri?
- Index(es):
Relevant Pages
|