Today's post is about Lotus Mobile Connect and how it can be used with
Traveler to make sure that mobile clients can reach the right Traveler
HA Pool or Traveler server, in a secure manner with a clientless VPN
First of all, many of you don't even know what LMC is. What is Lotus Mobile Connect? In a nutshell...
VPN solution supports all access points
● Laptop and Desktop (client)
● Handheld mobile device (client)
● Browser (clientless HTTP Access)
• Proven ROI - least cost routing & data optimization
● Network optimizations reduces network data costs
• Secure end-to-end connect to corporate intranets
● Strong authentication and support for RSA Secure ID
● End-to-end encryption: DES, Triple DES, RC5, AES and FIPS 140-2 certified
Clientless: No client software installation, application and platform agnostic!
Single Sign On: LMC Gateway + application authentication
– Same strong authentication and encryption algorithms as the LMC Mobility Client
– FIPS 140-2 certified platform. Contains latest secure SSL/TLS ciphers and industry standard authentication mechanisms
– Two way certificate validation available for additional layer of trust
– Configurable to run simultaneously with full VPN sessions. Multifunction, IT configurable remote-access solution (Example: Subset of users restricted to specific apps via clientless access only. Other set of users allowed expanded enterprise access with LMC Mobility Client.)
So what does it mean to be "Traveler aware"?
LMC 6.1.4 Traveler Aware Features
Recognition of Traveler URLs,
applies data flow optimizers and HTTP header tags,
previous password recognition (prevent LMC server lockout).
LMC 6.1.5 (NOW IN BETA!!) Traveler Aware Features
With the current set up of Traveler, a user has to know their URL to
their Traveler server or Traveler HA (High Availability) Pool. When
customers are deploying to large numbers of people, it can be a pain to
have so many profiles out there pointing to different Traveler servers
or pools. In the deployment that I just did, they are planning on 4
pools (I completed 2), each pool supports about 10,000 users. However,
this customer did not want to have 4 different possible Traveler
profiles on their Apple iOS Mobile Devices.
Enter the new LMC 6.1.5 Traveler aware feature...
The new LMC 6.1.5 Traveler aware feature allows LMC to go into a single
URL mode. LMC "learns" which server or pool of servers a user belongs
to, and makes sure that the user is routed properly. So in a High
Availablility scenario, you still need a load balancer in front of the
pool, but if you have more than one Pool, LMC will route the users to
the right pool. It knows how many users belong to each server or pool
of servers, and will divvy up new users to a less loaded pool. Pretty
cool, huh? Look for LMC 6.1.5 some time in Q3!