Hi,
First post so I should share my appreciation for developers of this site and the helpful users who have posted. Here at Carleton, we have recently begun customising and improving our Luminis product and the info I've found here has been super helpful.
Anyway, we would like to move the login page from the cp/home/loginf location where the index page redirects you to.
I've seen a few portals have done this. It appears to me that the redirects built into the luminis product are strictly for browser sniffing and cookie checking. If so it's no problem just including the javascript on the actual index page.
But I just wanted to know if anyone is able to varify that this is all that happens when users are getting redirected. What will I absolutely need to place on my new login page to make sure everything functions as it should?
Any help is greatly appreciated.
Cheers
Danny
Hi,
Hi,
We moved(?) the login page to the root of the site and we changed the default file type to .jsp so that we could include dynamic data (even though the JSP implementation is very basic.)
Basically what we did was we created our own HTML file in the root of the site. This overwrote a file that had some javascript or meta redirects so the user was no longer forwarded to the loginf page. On the HTML page we added our own browser tests (based on SCTs) and a login box, We also made it so that if the user is logged in, they will be pushed into the portal rather than seeing the login page (done in javascript).
This works well but there are a few other little items that need to be corrected. The logout- redirect, and incorrect username and password redirects need to be changed to point at the root. There are probably a couple other files that point at loginf that we needed to change also.
Now Loginf uses frames when it comes out of the box, and I believe that I put a redirect back to the root in there too.
Hope that helps
Dave