IBM has released a ST client on their Connections Cloud service that has SAML as a SSO option for a community but it states that it only works with (SAML) authentication to IBM Tivoli Federated Identity Manager (TFIM) servers. It doesn't support authentication to Microsoft Active Directory Federation Services (ADFS) (actually called Connections Chat with Connections Cloud)
Then there is also the Sametime 9.0 Wiki page called "Enabling SSO between a SAML identity provider and the Sametime Community Server" that states "The IBM® Sametime® Community Server supports Security Assertion Markup Language (SAML) single sign-on. When this feature is enabled, the Community Server can validate SAML assertions that are generated by a SAML identity provider (idP). This allows a client to authenticate by password to the idP, receive a SAML assertion, and then use that assertion to log in to Sametime, without having to re-enter the password. The Community Server can validate either SAML or LTPA (Lightweight Third-Party Authentication) tokens, but it can only generate LTPA tokens.
Yet IBM still tell me that ST Clients can't use SAML. Why is this page there then? http://www-01.ibm.com/support/knowledgecenter/SSKTXQ_9.0.0/admin/config/st_adm_security_sso_for_saml_and_comm_serv.dita
Has anybody tried to connect via SAML with Sametime? Maybe you have a Connections Cloud account and have downloaded the client and then tried to connect it to an on-prem Sametime Community?
Any thoughts or feedback. Is IBM reading?