I’ve been stuck for some time on the last piece of the SSO options in Luminis IV, namely the SSO to WebCT. I’m turning here for what I think must be a simple solution to an out of the box implementation.
The scenario plays out like this. I have an instructor, lshields, with course content in CE 6 and with synchronized passwords in both environments. When I go into the My Courses channel for this instructor, click on edit, say use WebCT class homepage and then save, the following errors appear in the cp.log file.
Malformed URL dummy_url/webct/public/serve_webctdb?OPERATION=find_wuui&DB=global&COURSE=xxxx&Global%20ID=lshields&AUTH=7124622b10ffddceff3e459c29112791
java.net.MalformedURLException: no protocol: dummy_url/webct/public/serve_webctdb?OPERATION=find_wuui&DB=global&COURSE=xxxx&Global%20ID=lshields&AUTH=7124622b10ffddceff3e459c29112791
Followed by:
Bad response from webct server: null
User lshields was not found in webct
Displaying error page to user: Can't service request to /cp/ip/login
Clearly Luminis is unable to find the user or course in CE 6 but, as far as I can tell the credentials supplied to both servers for the handshake is correct. There’s a conceptual piece or simple setting I must be missing. Any help is appreciated.
SSO to WebCT CE 6.2 from Luminis IV
We are running into a similar problem.
We are running Bb CE 6.2.3, with Luminis IV.0.1.17.
Have you found a solution to this yet? We are currently working with Sungard and Bb on the problem, the issue has been escalated to the Bb engineers.
It seems the problem is related to the fact that when Bb receives the SSO request from Luminis, it is sending back a malformed WUUI url as a response.
If you have had any luck finding a solution, please let me know. We have had Bb SSO offline for a few weeks now, our students and faculty are getting restless.
Thanks,
JBishop
The last place you'd think to look to fix WebCT SSO problems...
We just found a resolution to our Luminis IV to WebCT CE 6.2.3 SSO problems.
Sungard and Blackboard prescribed the following steps, which we followed:
When we installed CE 6.2.3, all of our Luminis SSO settings were blown away. We had to restore that setup.
We checked that our stored secrets in Luminis matched the stored secrets in Blackboard.
However, in the process of debugging our setup, one of the log preference files on the luminis side (running Red Hat) was saved in DOS format. Apparently, the WebCT CPIP connector does not like this, not one bit.
Thismorning I was updating my log preferences to send some additional info to our WebCT support tech, and found that one of the files was in DOS format. I saved it in the correct file format, and *tada* we had WebCT links working again.
I would recommend you start by checking these log preference files:
$CP_WEBINF/config/cplog4j.properties
$CP_ROOT/products/tomcat/tomcat-cpipconnector/conf/logging.properties
I had a glazed look of, "I can't believe that finally fixed it" look on my face for a good portion of my morning. While we initially did have to deal with WebCT 6.2.3 blowing away our SSO settings, it was our log preferences that eventually held up our WebCT links.
Hopefully that helps you as well.
Still looking for the solution
I've tried working with SGHE but have had no luck there at all. Currently my SGHE contact has opened a ticket with Bb because she had no idea how to resolve the issue. Heard from Bb tech support and to that end, I added an entry
log4j.logger.com.pipeline.sdk.cpip=DEBUG
to cplog4j.properties file expecting to see a cpip.log to help in the diagnosis but that didn't happen. Does anyone know if this has changed for Luminis IV? The cp.log file has better diagnostic messages as a result but the Bb consultant is telling me he can't help without a cpip.log file to review.
Luminis IV log files
There is no cpip.log in Luminis IV. All log messages from the Luminis web application go into cp.log. There is a cpipconnector.log, but that is for the GCF implementation.
thanks for the info
I appreciate the comment. What I was looking for showed in the cp.log anyhow. I'll pass this along to both the Bb and SGHE guys who apparently don't know that.
did you get sso running yet?
we have 4.0.2 sso to 6.2.3. I'd be glad to send you our conf info.
Please Yes!
Marcy,
I very much appreciate the offer. Luminis support belongs to me by default in addition to way too many other things, none of which I can devote the time needed to make them work well. Anything you have to share will be much appreciated. You can post here or send to my campus email account, aayers@massasoit.mass.edu.
Al
Yipee!
Marcy,
You saved my sanity, and a heck of a lot of my time. Thanks so much for sharing. I'm sure it didn't seem like much, but it was all I needed to look at your configuration and see the simple mistakes I had made. Isn't technology a wonderful thing when it works the way it's supposed to?
Al