LDN - Luminis Developer Network

Well I have been working for the past few weeks on getting Luminis 5 up and running in a Development instance.

We currently have LDAP and CAS and single sign-on for a bunch of Marist applications, and then we have Luminis 4 that has it's own LDAP and CAS and does not single sign us into other Marist applications. We use EAS authentication, so we actually authenticate against our LDAP, not the Luminis LDAP

Hi,

We are in the process of setting up a stand-alone CAS server, which would be used in conjunction with LP 5, in a Solaris 10 environment. I have some questions regarding this:

1. I would like to know if there are any hardware requirements/specifications for a dedicated/stand-alone CAS server. Besides Luminis and Banner, we plan to use the CAS server for SSO to about 10 other applications at our school. Does anybody have any recommendations for server hardware? (The LP 5 installation guide specifies a minimum of 25 GB of storage and 4 GB of memory for each of the LP 5 tiers.)

I'm getting the following strange error message.

It appears as though the UDCIDAuthenticationMetaDataPopulator.populateAttributes function is mistaking the callback URL for the UID. I have gone through the instructions in the Luminis Platform / Banner Integration Setup Guide / 5.0 several times now, and this always seems to be the result.

I have been looking through LDN, JSIG as well as Sungard FAQs in order to find materials to debug my issue, but so far I have had no luck.

I am trying to use Luminis's CAS server to SSO into a .Net application.  I edited my server.xml and web.xml files per FAQ 1-4YFLMR.

Has anyone investigated linking Sun OpenSSO with Luminis authentication server. 

Specifically allowing Luminis to trust the OpenSSO for authentication.

So a user with an OpenSSO authentication ticket can login directly into Luminis?

Thanks

We're in the process of upgrading to Luminis IV from uPortal and are investigating different single sign on strategies.  As many of the applications around campus use an CAS server, we're hoping to have Luminis use it as well.

One proposed setup would:

1. Use mod_auth_cas  (http://www.ja-sig.org/wiki/display/CASC/mod_auth_cas) to force the user to authenticate with CAS.

2. Grab the username from the session file mod_auth_cas creates

3. Look up the user's information (name, roles, etc) from our existing LDAP server.