I'm not sure that this is the right forum but perhaps it is. My SSL certificate is for *.domain.com and I have two other domains that are sharing the database. What is the most efficient way to force all secure activity to a subdomain URL (default SSL for login/register/etc)?

Maybe you have a better suggestion?

Thanks!

Thanks Joe. Perhaps this leads to a feature request, to enable a specific URL pathway (in my case secure.domain.com) for the SSL activity (mojo controlled already) but return them to the original domain after logging in.

In the meantime, what is the best way to setup the file structure and mapping to force the Mojo secured pages to a subdomain URL? instead of www.domain.com/secure/login.aspx how do I force it to go to secure.domain.com/[secure/login.aspx or just /login.aspx - doesn't really matter]?

I have setup the same secure.*.com subdomain for all three domains but I expect the other two that are not on the SSL certificate to indicate a certificate error when accessed. Chrome makes it much more obvious then IE or FF... so even an intermediate page that warns the user that they are going to a safe place to login but will be returned to their original page after logging in.

How can I send them to the certificated secure.domain.com to login and then return them back to the original domain in Mojo?

PS: So far, the URL Rewrite causes a 'too many redirects' loop due to the hostname mapping. Is there an easy solution that I'm overlooking?
Thanks!