It's been sometime since I've had a chance to post. My team also supports Quickr for WebSphere Portal, and needless to say - we've been busy. Let's briefly bring up LTPAToken2 support. LTPAToken2 has been around in Portal 6.0, but I seem to be getting the inclination that it may be a touted feature in Portal 6.1. LTPAToken2 is simply the next generation of LTPAToken Single Sign On (SSO) support. Those enterprises looking for more secure forms of SSO might find LTPAToken2 desirable. Beware of two limitations when moving to LTPAToken2:
1. DIIOP does not yet support LTPAToken2. This means that any custom code which leverages creation of Notes Sessions using a token must do so with the legacy LTPAToken. This will effect the Domino Extended Products portlets. Those Portals with heavy NotesView portlet integration should simply weigh the need for LTPAToken2 with the possible lack of features in NotesView.
2. The Sametime STLinks API does not support LTPAToken2 at this time. Within Portal, you can configure the STLinks API to pass a STToken rather than an LTPAToken2. This is fairly easy by setting useLTPAToken=false in the CSEnvironment.properties. The trade off is additional overhead in creating connections to Sametime to obtain a STToken.
The point here is to be aware that LTPAToken2 support available in Portal does not guarantee that legacy portlets will operate will the same feature support previously seen in Portal 6. When in doubt, test or give support a ring.[Read More]
Coding IBM Collaboration Solutions
Matching: ltpatoken2 X