Multi Server Sign-On (MSSO) and a bag of chips
Tags :Technical
We embarked on the greater task of implementing
a LTPA token and single sign-on across the whole product suite. Some
immediate things that could be done better (yes we know there is more)
- A simplified installer (Installshield or the like for Windows) on the Sametime cd#2 under toolkits that places the necessary files on the Sametime server and again that gets run for the QuickPlace server. Yes there is only a few files that must be moved around, but the directories don't even exist and it is just too much manual work.
- Adjust the stlinks.js and offline.gif files in the 6.5.1 release so you don't have to move them around manually for awareness to be correct in Domino Web Access.
- Set the choice for awareness for Domino Web Access to use tokens or LTPA as part of one of the installation advanced choices
- Remove the documentation conflicts for Sametime/QuickPlace integration that exist between technotes and steps to get the functionality working against a single LDAP directory. (for example one says never use the Sametime or QuickPlace server as the LDAP source while another says 'using the Sametime server for LDAP'. This confuses things later and leads to the next one.
- Make it easy to move between primary LDAP directories on the Sametime server. Moving from Domino Directory to LDAP was covered and documented, but not LDAP to LDAP as that becomes the required and directory of choice both for these.
Ok, I have one more issue that I will cover tomorrow around the new CA process.
blog comments powered by Disqus
On Thursday, February 19th, 2004 by Chris Miller