Connecting Tech Pros Worldwide Help | Site Map

Forms authentication - different domain for login

 
LinkBack Thread Tools Search this Thread
  #1  
Old January 29th, 2007, 08:15 AM
JDC
Guest
 
Posts: n/a
Default Forms authentication - different domain for login

Hi all,

I have an ASP.NET application for which I'd like the "login" page to
be secure. The problem I have is that while my hosting company gives
me a "secure" option, secure pages appear under a different domain.

For example; my application is hosted here:
http://www.example.com/myapp/

But pages uploaded to the "secure" folder appear here:
https://somesecureserver.com/example/

I don't want to put the whole application in the secure folder, so is
it possible to have a login page at https://somesecureserver.com/
login.aspx that authenticates the user for my application at http://
www.example.com/myapp/ ...?

Thanks in advance,

JDC


  #2  
Old January 29th, 2007, 03:25 PM
bruce barker
Guest
 
Posts: n/a
Default Re: Forms authentication - different domain for login

to share a login cookie, your site domains must have a common root with
at least one dot. otherwise you can use url encoding (cookieless sessions).

-- bruce (sqlwork.com)

JDC wrote:
Quote:
Hi all,
>
I have an ASP.NET application for which I'd like the "login" page to
be secure. The problem I have is that while my hosting company gives
me a "secure" option, secure pages appear under a different domain.
>
For example; my application is hosted here:
http://www.example.com/myapp/
>
But pages uploaded to the "secure" folder appear here:
https://somesecureserver.com/example/
>
I don't want to put the whole application in the secure folder, so is
it possible to have a login page at https://somesecureserver.com/
login.aspx that authenticates the user for my application at http://
www.example.com/myapp/ ...?
>
Thanks in advance,
>
JDC
>
  #3  
Old January 29th, 2007, 05:15 PM
GroupReader
Guest
 
Posts: n/a
Default Re: Forms authentication - different domain for login

You *can* share authentication information between servers (like in a
server farm situation)... but you probably won't be able to do it in
the web-hosting situation you described. You would need full access
to both servers to make sure the authentication and encription details
are the same on both servers (in machine.config). Also, I guess this
only works for similar domains like Bruce stated above.

Another note: I seem to recall an article about "typical security
pitfalls." If you secure your login page, but do not secure the rest
of your application, it makes it really easy for a hacker to gain
access to your authentication cookie which is passed with every
request. The hacker gets the cookie from one on the non-secured
pages, then can resend that same cookie to any of your secured pages.
Something like that. I'm no expert.


 

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Popular Articles

What is Bytes?

We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights. Get the best answers to your questions from over 220,662 network members.