266 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
IBM Sametime HTTPS redirection
Fri, Jul 24th 2015 92
Sametime meeting widget on IBM Connections 5.0 CR02 – error 403
Tue, Jun 16th 2015 21
URL preview in IBM Connections 5.0 CR02 – ifix LO84882 required to work with forcedConfidentialCommunications enabled
Fri, May 29th 2015 28
Sametime and POODLE SSLv3 patches
Wed, Feb 25th 2015 23
IBM Sametime Community server does not upgrade due to SSCEncodedAuthorization
Fri, Feb 20th 2015 13
New Sametime Proxy APNs test application
Fri, Feb 6th 2015 25
LDAP error code 49 – Failed, invalid credentials – user cannot log in to Connections
Thu, Jan 8th 2015 29
Top 10
IBM Sametime HTTPS redirection
Fri, Jul 24th 2015 92
LDAP error code 49 – Failed, invalid credentials – user cannot log in to Connections
Thu, Jan 8th 2015 29
URL preview in IBM Connections 5.0 CR02 – ifix LO84882 required to work with forcedConfidentialCommunications enabled
Fri, May 29th 2015 28
New Sametime Proxy APNs test application
Fri, Feb 6th 2015 25
Sametime 9 business cards revisited and beaten!
Thu, Aug 21st 2014 23
Sametime and POODLE SSLv3 patches
Wed, Feb 25th 2015 23
Sametime meeting widget on IBM Connections 5.0 CR02 – error 403
Tue, Jun 16th 2015 21
Sametime meetings not working in STProxy web client
Wed, Dec 17th 2014 19
Solution for Sametime connection issue with iNotes when SSL is used
Thu, Jun 26th 2014 16
CCM/FileNet search index fails in IBM Connections 4.5 due to special character
Mon, Sep 22nd 2014 16




Recent Blog Posts
92
IBM Sametime HTTPS redirection
Fri, Jul 24th 2015 12:39p   Ben Williams
A
21
Sametime meeting widget on IBM Connections 5.0 CR02 – error 403
Tue, Jun 16th 2015 9:25a   Ben Williams
A
28
URL preview in IBM Connections 5.0 CR02 – ifix LO84882 required to work with forcedConfidentialCommunications enabled
Fri, May 29th 2015 8:44a   Ben Williams
A
23
Sametime and POODLE SSLv3 patches
Wed, Feb 25th 2015 5:30a   Ben Williams
A
13
IBM Sametime Community server does not upgrade due to SSCEncodedAuthorization
Fri, Feb 20th 2015 10:08a   Ben Williams
A
25
New Sametime Proxy APNs test application
Fri, Feb 6th 2015 9:47a   Ben Williams
A
29
LDAP error code 49 – Failed, invalid credentials – user cannot log in to Connections
Thu, Jan 8th 2015 5:11a   Ben Williams
A customer had a problem with a single user not being able to authenticate with Connections. The user had an active profile and they use Domino LDAP. The SystemOut.log showed. [1/5/15 13:27:31:824 GMT] 00000190 LTPAServerObj E   SECJ0369E: Authentication failed when using LTPA. The exception is com.ibm.websphere.wim.exception.PasswordCheckFailedException: CWWIM4529E  The password verification for the ‘juser’ principal name failed. Root cause: ‘javax.naming.AuthenticationExce
19
Sametime meetings not working in STProxy web client
Wed, Dec 17th 2014 11:11a   Ben Williams
I found that for a customer the meetings icons in the STProxy web client wasn’t bringing up the user’s meeting rooms. After a bit of debugging server trace showed that an LtpaToken was being generated but the browser wasn’t getting an LtpaToken returned to it. It drove me made because the STProxy doesn’t need to have SSO enabled for it to work like the Meeting server does, regardless of that, SSO worked in all directions between the Community server and the Meeting server
14
Sametime 9 policies not working due to slashes in the policy name in SSC
Fri, Dec 5th 2014 6:11a   Ben Williams
I had come back on site to a customer to deploy some other Sametime 9 services and found that the managed-settings.xml wasn’t being applied to the clients. I remembered reading Gabriella Davis’ blog http://turtleblog.info/2014/04/02/problems-deploying-sametime-policies-the-missing-link so I found it and at first I enabled POLICY_DEBUG_LEVEL=5 and then updated console.properties adding  SSCUserName, SSCPassword and removing SSCEncodedAuthorization. I added the following trace to STCo
13
Cannot edit Media Manager policies due to incomplete xml data in DB2
Tue, Nov 25th 2014 11:10a   Ben Williams
I had a few problems with a customer’s deployment of Sametime 9 which probably come down to deployment plans and the order of the servers being installed. During installation I had problems detailed in “System version is null” on new IBM Sametime Video Manager installation which forced me to uninstall the VMGR and install again with a new deployment plan. The outcome of this was that I could not administer the default policies nor create new Media Manager policies in the SSC, I saw the




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition