Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Tutorial on setting up SSL in DNN 4.5.4+Tutorial on setting up SSL in DNN 4.5.4+
Previous
 
Next
New Post
7/24/2007 8:13 AM
 

As long as you login using the same host name and domain name then you will still be logged in.  If you are using a shared certificate then this is probably not possible.

----

Mods: Please move this thread to the Chat About It forum.


DotNetNuke Modules from Snapsis.com
 
New Post
7/24/2007 1:16 PM
 

If that is true, then wouldnt DNN be limited to one domain per installation, in that case?

 
New Post
7/24/2007 1:33 PM
 

No. It is the way the authentication is done. To put it in a very simple way, it saves domain with the fact that user is authenticated and that's how it is checked. So, if you are logged in on https://yoursite.com and then redirected to http://www.yoursite.com, this won't work either. Only identical domains checkout correctly.

You can entertain yourself by navigating to your site, login in on www.yoursite.com and then siwtching to yoursite.com without the www...


Vitaly Kozadayev
Principal
Viva Portals, L.L.C.
 
New Post
7/24/2007 1:37 PM
 

The login authentication cookie is saved for separately each host name and domain name on a DNN install.

If you happen to have more than one host name . domain name combination pointing to the same portal and a user switches to a different one then they will be logged out.

This is by design.  The concept of having more than one host name . domain name pointing at a DNN installation is usually to seperate the different portals within one DNN instance, so you can't login to one portal and get access to another.

This is right in line with my opinion about it not being good practice to use a shared SSL certificate for multiple portals or for multiple IIS websites.

 


DotNetNuke Modules from Snapsis.com
 
New Post
8/4/2007 1:19 PM
 

Can you recommend what SSL to use, if not a shared SSL certificate, when you are faced with potentially many subdomains at yourdomain.com or need to set up portal aliases for your customer's subdomains or www domain names, ie customersub.customerdomain.com or www.customerdomain.com?

I tried to ask that question here:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/-1/threadid/158402/scope/posts/Default.aspx

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Tutorial on setting up SSL in DNN 4.5.4+Tutorial on setting up SSL in DNN 4.5.4+


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out