Tuesday, December 6, 2011

SnTT- One way to troubleshoot SSO problems in WAS

This was a Mashup Center server and a Connections SSO integration on Websphere.
Prior to upgrading Connections from 2.5 to 3.0 it worked fine. But some place in the upgrade this, and some other internal items, broke. I was asked to lend a hand at troubleshooting it.

I first asked the Wizard of WAS, Dave Hay if there was anything I should know about Mashup Center as I have never used it. His help in discussing ways to troubleshoot this is greatly appreciated.

For the newbie and even someone who scratches their head at the Websphere Admin Console, sorry the Integrated Solutions Console, it is a bit confusing but once you get  the hang of bits of it you will be fine.

I am not going to go over how to set up the SSO but how to enable the trace and logs to help you get tot he bottom of the problem.

This could be used for any one needing SSO troubleshooting for WAS in general.

  1. Login to the WebSphere Admin Console
  2. Go to Troubleshooting -> Logs and Trace,
  3. Select the WebSphere server in question,
  4. Then click on Diagnostic Trace,
  5. And then choose Change Log Detail Levels,
  6. You will see a *[All Components] with a twistie (+ sign)
  7. Click on the expanded twistie and scroll down until you find .com.ibm.ws.*
  8. Click on this one's twistie and find  .com.ibm.ws.security.*
  9. Now click on the whole reference to  .com.ibm.ws.security.*
  10. And you can select the level of traces, in this case I selected the All messages and traces since we did not know what area exactly was failing.
  11. This will change the text in the box above the list to: *=all for the selected item.
  12. Click Apply, Save, OK
  13. Restart WAS
To revert it back, change the *=all to *=info and then
Click Apply, Save, OK
Restart WAS

So what will you get and where is it found?

  1. Login to the WebSphere Admin Console
  2. Go to Troubleshooting -> Logs and Trace,
  3. Runtime Messages and expand it
  4. Open Runtime Error
  5. You should now see towards the bottom a list, if any, of the errors and with code and references to help you troubleshoot your problem.
In our case we had an incorrect ou that appeared twice breaking everything. But we also had some other tinkering.

Good luck

1 comment: