Christin L. 19.Apr.13 05:22 AM a Web browser Sametime Mobile 8.5.2 IFR1 Windows
This is FYI since I stumbled over this problem during my pilot and addressed the issue with a PMR. In case you are facing the same dilemma, just add your PMR to the APAR/SPR:
I have installed a Sametime Proxy server 8.5.2 IFR1 in the DMZ in a standalone installation to grant chat functionality to mobile iOS devices outside the LAN. I had 15 Pilot users and wanted to restrict the access exclusively to them. Normally anyone having the Chat App installed and knowing the Proxy Server alias, can set up the community and use the App. There is no way for an Admin to restrict the usage of the App to a certain user group. :(
There is however the setting "Allow mobile clients" in Sametime policy on the community server BUT this does not influence the Proxy server at all! So dont be surprised if you try it invain.
I opened PMR 43905,124,848 and was told the following:
Regarding this problem we have an internal technote:
Sametime Policy Not Restricting Mobile Clients
Product: IBM Sametime > Policies > Version 184.108.40.206
Platform(s): Google Android, Apple iOS
In the default Sametime policy, the setting 'Allow mobile client' is not selected. iPhone and Android users are not prevented from logging into Sametime.
Diagnosing the problem:
The 'Allow mobile client' option is only valid while accessing the Sametime Community Server with a Mobile device (older mobile devices like Nokia, Blackberry etc.). The option does not have any effect to
the Sametime Proxy which will be used for authentication via iPhone or Android devices.
Resolving the problem
There is currently no option to avoid the login of iPhone and Android mobile devices with the Sametime Application at the Sametime Proxy Server. APAR # LO72335 (SPR #IKHN8ZEJ2K) has been opened to address this functionality.
Unfortunately the is no way at the moment to restrict the access for the mobile users via iOS or Android devices to the ST Proxy Server.
APAR # LO72335 has been raised as an enhancement request and it is planed to fix the issue in the next Sametime release.
So... add your PMRs to get that fixed rather sooner then later :)