You are here

External System Error

Submitted by psilwal on Mon, 06/24/2013 - 12:01

Hi,

Only few users are getting this error:

External System Error
CPIP Notification:loginuser request failed for sctssb
If you need assistance, contact your system administrator.


Any ideas on this?

Thanks,
Prak

Luminis Version:

Hi,

Please check the Luminis application log files in $CP_ROOT/logs for more information on exactly what part of the SSO is failing. The files generated and output verbosity vary depending on your logging settings but you can probably find a stack trace in cp.log at least.

Good luck!

Tom

Tom,
This is the log found in cp.log

[2013-06-24 08:31:43,665] [ERROR](DefaultURLRequestBroker.java:915) {pool-1-thread-47} [com.pipeline.web.DefaultURLRequestBroker]: getResponse failed for https://banner.school.edu:443/prod/gokssso.p_cp_login_sserv?sid=B%2FF5Cd...
java.io.FileNotFoundException: https://banner.school.edu:443:443/prod/gokssso.p_cp_login_sserv?sid=B%2F...
Caused by: java.io.FileNotFoundException: https://banner.school.edu:443:443/prod/gokssso.p_cp_login_sserv?sid=B%2F...
[2013-06-24 08:36:55,472] [ERROR](DefaultURLRequestBroker.java:915) {pool-1-thread-33} [com.pipeline.web.DefaultURLRequestBroker]: getResponse failed for https://banner.school.edu:443:443/prod/gokssso.p_cp_login_sserv?sid=Oq6X...
java.io.FileNotFoundException: https://banner.school.edu:443:443/prod/gokssso.p_cp_login_sserv?sid=Oq6X...
Caused by: java.io.FileNotFoundException: https://banner.school.edu:443:443/prod/gokssso.p_cp_login_sserv?sid=Oq6X...

Hi,

Assuming you didn't modify the contents of the log file before posting it, I would say your middle tier configuration settings are wrong.

For example, here is an excerpt of the first getResponse error:
getResponse failed for https://banner.school.edu:443/prod/gokssso.p_cp_login_sserv

Your portal is attempting to use banner.school.edu as the hostname for SSB.
I would recommend reviewing your settings in configman:
$ configman -g es.sctssb.configURL

As well as your settings in the LDAP under sctssoapplications.

I would also recommend resetting the user's password since it's output with verbose logging.

Thanks,
Tom

Hi Prak,

The 404 that you're indicating coming from the Banner server can occur for a number of reasons. It's possible that your settings for the middle tier integration are not configured properly but I would expect that type of mistake to affect the majority of users and not a small subset.

Another common issue involves user mapping. If the middle tier integration is unsuccessful in identifying either the Banner or Luminis account the SSO will fail with a similar message. Typically this is the case when the LDAP settings in GUAUPRF are incorrect or your settings are pointing to a different Luminis instance after a Banner clone.

Without having a better idea of the whole picture it's hard to say where you should focus your time right now. I would recommend reviewing the middle tier configuration from the Luminis configman settings to the LDAP settings. If you cannot find anything wrong there you may want to look at individual accounts where the issue is reported.

Sorry I couldn't provide more specific information but I hope this helps!

Tom