Using another 3rd party tool instead of a native Sametime connection?
Tags :Announcement
Apparently some big companies do not want
their users utilizing such things as the IBM
produced hook for Trillian,
GAIM
or even some business partner products to access Sametime (what are you
doing over there Carl?). A new technote shows how to block these
outside clients (even Stlinks) from your Sametime server.
| Problem |
| The Sametime Toolkits allow a variety of ways to connect to a Sametime server. Is there a way to see which users are connecting with a custom built client, and can I prevent those users from connecting? |
| Content |
| The Sametime server can be configured
to allow only certain clients to login based upon their unique Client ID.
Today, clients who login to Sametime declare their login type upon
login. C++ Connect clients use login type of value 0x1000 Java Connect clients use login type of value 0x1001 C++ toolkits, by default use login type of value 0x1002 (can be configured in the toolkit API) C++ toolkits, by default use login type of value 0x1003 (can be configured in the toolkit API) Sametime links clients, use login type of value 0x100A It is possible to configure the server to allow only specific client types to login to Sametime. In the [Config] section of the sametime.ini, under[Config] use the flag VPS_ALLOWED_LOGIN_TYPES to specify the allowed login types. The flags affects all logins where this Sametime server is the home server. By default (if this flag is not specified) all login types are allowed. Example: [Config] VPS_ALLOWED_LOGIN_TYPES=1001,1002 Note: The client filter is only available on: Sametime 3.0 IF3 Sametime 3.1 with a hotfix. Please contact Lotus Technical Support for a copy of the fix. Sametime 6.5.1 |
blog comments powered by Disqus
On Thursday, June 23rd, 2005 by Chris Miller
