Login Destinations
Permalink Browser Info Environment
Hi Mainio,
I want to set up two company websites on one install of C5 so they can share product information. When someone logs into one of the sites how does login destination work? If I log in from domain1 do I get directed to domain1's home page and logging in from Domain2 directs to domain2's home page?
Also i am assuming if I am logged into domain1 then go to domain2 I will already be logged into the second domain?
Thanks
Peter
I want to set up two company websites on one install of C5 so they can share product information. When someone logs into one of the sites how does login destination work? If I log in from domain1 do I get directed to domain1's home page and logging in from Domain2 directs to domain2's home page?
Also i am assuming if I am logged into domain1 then go to domain2 I will already be logged into the second domain?
Thanks
Peter
Type: | Pre-Sale |
---|---|
Status: | In Progress |
Sounds good on the first questions. On logins, I would use the same user name and password for logging into both sites, correct? Can I log into both simultaneously or use the stay logged in for two weeks option at login and remain logged in to both?
Yes, you use the same username+password for logging into all the sites.
And yes, for each domain individually you should be able to use the "remember me" option too. Think of them as separated sites to which you have the same user account.
And yes, for each domain individually you should be able to use the "remember me" option too. Think of them as separated sites to which you have the same user account.
Hi again, A couple last questions,
What about single pages? Do both domains use the same single pages?
And searching, if a search block is set to everywhere does it return everything in both domains?
Thanks
What about single pages? Do both domains use the same single pages?
And searching, if a search block is set to everywhere does it return everything in both domains?
Thanks
Single pages:
Only the pages under that page that you map for the domain will be automatically accessible for that domain. However, you are able to set each page anywhere else in your sitemap (including single pages) an attribute called "Allow From All Domains". This makes the page accessible from each domain.
Search:
Multiple Domains does not touch how search works. In the search block itself you are able to set it to search beneath a specified page, so you can set your search so that it only searches under the specified pages that are beneath your domain.
Only the pages under that page that you map for the domain will be automatically accessible for that domain. However, you are able to set each page anywhere else in your sitemap (including single pages) an attribute called "Allow From All Domains". This makes the page accessible from each domain.
Search:
Multiple Domains does not touch how search works. In the search block itself you are able to set it to search beneath a specified page, so you can set your search so that it only searches under the specified pages that are beneath your domain.
For the first question: yes, this is by default how c5 works and Multiple Domains does not actually change anything about that. So, if user logs in from domain1, they stay at domain1 unless you have setup your own redirects after the login, e.g. through another add-on.
The second question, this is a bit more complicated. The short answer is that no, Multiple Domains does not make this happen automatically. Multi-domain cookies are generally forbidden by any server side programming environment, including PHP. This is generally considered as a good security practice and also cookies are meant to be domain specific. This prevents the PHP session to be shared across domains and therefore also concrete5 logins.
There is a way to get around that if you are only using subdomains for a single main domain but if you are using completely different domains, you cannot achieve this easily.
If you need multi-domain logins you would need to think of an SSO solution for your website where you have an authentication service running in its dedicated domain and all your additional domains are authenticated through that. You could possibly make the authentication flow seamless when people change from domain to another but obviously there is some amount of programming work involved in that.
Let me know if any other questions arise! I hope these answer your initial questions.
Best,
Antti / Mainio