LDN - Luminis Developer Network

Mulling over our cpip connectors made me realise that we should certainly not be using port 8008 as the cpipconnector port - particularly in the case where you are using pickup response rather than putting pickup.html on the external system. The obvious reason is that 8008 is very likely to be providing authentication info to the user's browser, albeit in a form that the user hardly notices, and then submitting it securely to the external system. And port 8008 isn't secure as it stands.

We've been having a problem with the built in channels - particularly (considering their importance) the campus and personal announcements. These last are high in importance to many of our staff users who see a useful granularity here that isn't really available so readily elsewhere. Sungard seem to have worked out the problem - that it's some kind of incompatibility between portlets and channels - and perhaps relates to the underlying uPortal implementation.

We decided to create our first SSO into our student e-Vision system. This entry may remind me how we did it when I do another one a little down the road. Doing our SSO involved getting to grips with pickup.response since I don't think there's much chance we would have a pickup.html put on the e-Vision server. It wasn't a particularly difficult SSO but we did take a day or so getting the various bits of configuration right.

The most notable thing from creating the SSO was using the pickup.response.

We have a problem with our test system. We are behind a proxy server, and we are using the Universal RSS channel for bringing in RSS feeds - so we set the proxy server so luminis can get the RSS feeds properly. But then we found that the proxy server was being applied to the connection between the luminis portal and the cpipconnector servlet. So we switched it off. We wanted both cpipconnector (of course) and RSS feeds on our test system, so we tried using the documented java system property of nonProxyHosts. This made no difference.