LDN - Luminis Developer Network

As promised at Summit 2008, attached here is the code and documentation for the U of S custom Luminis API. This API exposes portal data to your application developers.

I'm not sure if the installation instructions are complete; if you do try to install this API, and you stumble on anything, please let me know. I'd like to make the instructions as good as possible.

Thanks,
Todd

At U of S, we assign some temporary passwords to students and then mail them a letter with their temp password printed on it.

If a student attempts to log in with a temp password, then instead of getting into Luminis, we send them over to our identity management web interface, where they need to set a permanent password.

I have removed the java code for generating and comparing temporary passwords, so it may not compile as-is. However, you will get the basic idea. Also, you will see where we set a cookie on login. You could set your own cookie as needed.

For quite a while, we have seen single sign-on from Luminis to Banner break when our systems are under heavy load (ie: registration, start of term) The errors in cp.log look like this:

[2007-03-09 14:43:13,063] [ERROR] WebServlet [cpip]: CPIP ERROR sct The system 'sct' is responding too slowly, please try again after a short wait
[2007-03-09 14:43:41,403] [ERROR] WebServlet [cpip]: CPIP ERROR sct The system 'sct' is responding too slowly, please try again after a short wait

Some times I have to log into a specific front end web server in our Parallel Deployment environment. Up to today, I've been editing the session cookies by hand using a Firefox extension. What a pain. So, I made a page for myself that simplifies the process:

https://paws.usask.ca/choose.html

In testing out Luminis IV, the feature that our users were drooling over the most was the new calendar channel. We've been waiting for this since 2004, back when Mike Z first teased us with it at a uPortal conference! So we were a little disheartened to realize that (a) we weren't moving to Luminis IV as soon as we wanted to, and (b) the new calendar channel couldn't be backported to Luminis III without doing too much work.