If UserLogin is allowed to land on a Luminate Online page that the Remember Me cookie will be properly set. In order to allow this to happen, the link needs to direct UserLogin to go to a Luminate page which then redirects back to Luminate Online Content Management System (CMS). That involves setting the NEXTURL hidden input element in your login form and creating a landing page that will receive a session variable with the URL of the page we really want.

Here's some example code for a Luminate login form:

<form name="lLogonForm" method="post" action="http://{your domain}/site/UserLogin">
	<input type="hidden" name="NEXTURL" id="NEXTURL" value="http://{your domain}/site/PageServer?pagename=cookieSet&s_redirectPage=[[S8]]" />
	<p>
		<label for="USERNAME">User Name:</label><br />
		<input type="text" size="10" name="USERNAME" id="USERNAME" value="" maxlength="60" />
	</p>
	<p>
		<label for="Password">Password:</label><br />
		<input type="password" size="10" name="Password" id="Password" maxlength="20" />
	</p>
	<p><input type="submit" name="login" id="login" value="Login" title="Login" /></p>
	<p> <label for="RememberMe">Remember me?</label>
		<input type="checkbox" name="RememberMe" id="RememberMe" value="RememberMe" />
	</p>
</form>
I'll go through this step by step.

The first thing to change is {your domain}. Since your CLO and CMS sites use different domain names you'll have to set this properly for the form to find the UserLogin form on your site. You can just browse to your CLO login form and then copy the URL from the location bar in your web browser.

Make the same change to the hidden input element named NEXTURL. This value tells UserLogin where to go.

You've probably seen PageBuilder URLs before. In this case, you're telling UserLogin to go to a page named cookeSet after the user logs in. You might not be familiar with session variables. The bit after & is where the session variable is set. The prefix s_ means, "create a session variable with this name and set it to this value." The [[S8]] means, "give me the URL of the current page. So once this URL is loaded the session variable redirectPage will be available and will be the URL of the CMS page that the user was looking at when they decided to log in.

The next step happens on page cookieSet. Here is the sample code for that:

<meta http-equiv="refresh" content="0;URL='[[?xxnullx::x[[S80:redirectPage]]x::{default page}::[[S80:redirectPage]]]]'" />
<h1>Thank You</h1>
<p>You are logged in. If you are not redirected to the page whence you came, please click the link below:</p>
<p><a href="[[?xxnullx::x[[S80:redirectPage]]x::{default page}::[[S80:redirectPage]]]]">[[?xxnullx::x[[S80:redirectPage]]x::{default page}::[[S80:redirectPage]]]]</a>

The first thing is a meta element that tells the browser where to go and when.

You will need to change {default page}. If the redirect session variable fails for any reason then this will be the page the user sees next. The rest of the content is there in case the reload takes too long or the user has that feature blocked in their browser.