Single Sign-on for Webseal and portal handy notes

Two deep-impact points:

1. For the portal cluster structure, generate LTPA on the DM. Synchronize the configuration by selecting the option to sync to each node via preferences.

2. There are many detailed configuration documents on the net, the result of my own configuration is not successful, the evening leader with a debug only left a portal one IHS start testing the whole process from the beginning in Webseal. Found from the IHS can access/wps/mypotal and from webseal cannot, view log discovery IHS Access/wps/myportal will redirect to/wps/redirect first, then redirect to/wps/portal and generate cookie information, Webseal Access/wps/myportal, however, shows no access and no cookie information generated after jumping/wps/redirect. Analyze each server log one at a time discovery of SystemOut.log LTPA token authentication under the Portal profile fails due to token expiry, checking system-discovery is a problem with webseal, and single sign-on succeeds after changing webseal time.

A system time does not cause a single point of failure indeed a bit of a sigh. Calm down to the finishing process only to find themselves too far to the final goal: a single point of failure to quickly check the single-point-related ltpa. It's a matter of being paranoid about a bunch of unrelated things.

To configure a single point of failure, you should first ensure that webseal-to-portal junction is correct, and if you have access to the portal through two logins, then check the single-point ltpa for problems. If there is a problem with webseal, then how to check ltpa is useless. Note this here, remind yourself to troubleshoot the problem must pay attention to things successively.

This article is from the "Sky Kill" blog, please be sure to keep this source http://1645027.blog.51cto.com/1635027/1409034