LDN - Luminis Developer Network

I'm doing a bit of analysis and was wondering if someone could further clarify my research concerning how Luminis is using the passwords for other systems.

It is my understanding that when Luminis is told the password, it then SHA encrypts the password with the key being Luminis's actual login password. That way nobody can just unencrypt the 1 password unless they know the other.

Is this the way it works?

I am seeing this error for the first time. We have the Banner integration and I see this error in our datapipeline-audit.log. This is only for some new users. has anyone seen this error before. Thanks

ERROR processing PERSON entity with identifier 'username' : not initialized

pp

I have a CPIP connection that needs to be removed from a user account every once in a while.

I try deleting it at the command line, but Luminis errors. I think this error is by design actually:
*****************
cptool set user userName -d ExternalAccount=easName
ERROR: Unexpected exception
Cannot delete ExternalAccount from Person
com.pipeline.sdk.mapper.PropertyNotFoundException: Cannot delete ExternalAccount from Person
at com.pipeline.sdk.mapper.PersonMapper.deleteProperty(PersonMapper.java:483)

Recently, I've begun to manage a tiered environment. In the past I had only handled Luminis setups that were confined to 1 box.

For this maintenance, I'm discovering a very confusing task to be configman settings. Some are specific to a box, some are not, but you can get yourself in trouble if you run:
configman -x config.configman
configman -i config.configman

there is the potential to overwrite specific settings on the other box.

Hi all!

I am working on a script that we would use when we need a Banner outage. The script will basically redirect all SSB/INB links to an outage page and change the banner channels' audience in order to hide them. All is done and working in development! ...Except that the new channel audience rules do not get pushed until Tomcat is restarted. The whole point of the script is to avoid Luminis restart.

When the user selects the INB link from within luminis, they are presented with the standard INB username and password message box rather than passing through the username and password from Luminis.

I have confirmed that the Luminis username = immutable ID = banner id and that the luminis password = banner password.

I'm not seeing anything that raises any eyebrows in the cp.log or cpip.log files.

Any advice is appreciated.

Thank you,
Dean McMinn
Eastern Washington University

Hello Everyone,

I was curious for those schools that migrated to gmail as their choice for email and calendar did you use google apps directory sync to initially populate Google Apps? From what Sungard has told me is that they use a xml extract from banner and that is how they populate google apps. If anyone has any advice I would greatly appreciate.

Thanks,
Mike

We are brand new to Luminis and have run into an issue, and I am hoping someone with more experience will be able to advise us on how to handle this situation. Along with Luminis we are integrating with D2L. Before we installed Luminis onto our production server it was decided that we would use the spriden_id as our login to Luminis. Now that we have begun our pilot training, a few users have decided that they do not like the fact that their spriden_id shows up in the from part of the email address in D2L.

We have been using EAS to Active Directory, Exchange 2007 and Windows Server 2003, as the main authentication source for our Luminis (4.2.x, Solaris SPARC) platform. The campus is going to upgrade both to Exchange 2010 and Windows Server 2008 R2 Enterprise in this coming summer. I would like to know if we will still be able to use our EAS to AD integration afterward. Any comment, suggestion, advices, or experience sharing will be greatly appreciated.

This year at Summit I presented a home grown JSP application that I coined "Luminis Logger". Here at Lehigh University we needed to have better, quantified data on who's logging into our portal, how often, what roles, etc... This home grown application has met that need.