Clientless Remote Access
Clientless Remote Access Answers from the Clientless VPN Experts
WHAT DOES "CLIENTLESS" MEAN?
To be deemed "clientless," a clientless remote access solution does not require an administrator to manually install a fat client component to the computer that is to be used for remote access. This reduces the administrator's work load while increasing the accessibility of remote access. With no pre-installation or pre-configuration required, an authorized remote worker can utilize any computer, anywhere in the world, to securely access their corporate resources.
Typically, the terms "clientless remote access", "clientless VPN" or "clientless access" are associated with the use of SSL VPNs to provide remote access. Usually, SSL VPN remote access is entirely browser-based, including proxied Web applications. When required, a "virtual" client is automatically pushed through the Web browser in the form of tiny Java applets (ROAM) or ActiveX controls. Unlike an IPSec fat client, SSL VPN thin clients are stateless and do not have to be manually installed or configured. SSL VPN clients are delivered transparently through the Web browser to any computer, on demand.
What is the difference between ROAM and other SSL VPN vendors?
ROAM uses a Java based rewriter to provide clientless remote access, allowing users of ROAM to securely access their applications from any computer with Java without requiring administration rights. ROAM also supports a wider array of applications for clientless access than other VPN vendors. Compared with products that require administration rights, a thin client install and limited support for non web based applications, ROAM supports a wider array of applications, faster deployment times and reduced support costs.
How does AnyWare Group provide clientless remote access?
ROAM's clientless SSL VPN Platform utilizes the Embedded Security Agent, a port forwarding agent with a proxy rewriter that provides simple, secure access to most systems and applications. Once established, the ESA is embedded in the ROAM portal desktop and remains open until the user session is ended.
- Clientless access controlled by user's "role"
- Secure encrypted tunnels, created for individual applications or systems
- Supports industry-leading virus and firewall products
- Supports load-balancing and fail-over
- Supports 2-factor authentication methods
- Administration rights are not required on the PC in use
- Perfect for Web applications, published applications, emulated applications and legacy systems
- Can authenticate against the organization's Active Directory by role or user account.
- Provides SSL security from 128 to 1024 Bit within a standard web browser.
Because it's clientless, there are no downloads or configuration issues to consider. The embedded security agent is "seamless" for your users and "touchless" for your IT department. ROAM never touches your organization's data.
How do other vendors provide clientless remote access?
To set-up clientless remote access, most vendors require you to purchase an SSL appliance and application gateway, renewable L2 & L3 Support contracts, load balancing/resource management, licenses for items like administration, malware protection, high availability and business continuity; and then purchase the necessary training to configure access to legacy systems and applications.
Typically out-of-the-box appliances only provide clientless access to web services, with vendors often requiring that the user download a client in order to access mainframe or client-server applications. The installation, reinstallation, management and support of clients in a distributed or mobile work environment is a large IT expense and a significant generator of help desk calls. In contrast, with ROAM, any browser equipped PC can securely access the vast majority of applications within an organization, without a client.
Even the simplest configuration of a manufacturer's SSL VPN appliance will include configuring an identity certificate; enabling access; creating group policies; creating a connection profile (tunnel ); configuring translation of IP addresses and port numbers; and configuring user accounts -- and that's before you enable Outlook Web Access, legacy systems and applications. These projects usually require expensive training and support.
When accessing a clientless portal, what applications do you need?
Clientless access technology can be used by anyone with a standard browser and an Internet connection.
Can a clientless solution access as many applications as IPSec VPN?
ROAM's clientless solution provides access to most of the file shares, systems and applications in an organization -- even hospitals, where proprietary applications and systems represent unique complexities. On the other hand, an IPsec VPN is usually best for establishing a VPN between fixed end-points, such as two offices. When supporting roaming users, an SSL VPN solution is the preferred choice because it requires no installation or configuration on the client machine and enforces endpoint security.
Does the clientless ROAM portal require the installation of any software?
ROAM clientless remote access only requires a standard Web browser and the basic version of JAVA found in most Web browsers. In the unusual instance where a browser does not already have JAVA installed, the user can immediately download the necessary version of JAVA, as long as the user has administrator-rights on the computer. Users do not need administrator rights on their computers for clientless remote access through ROAM.
When accessing the clientless portal, how do you set up your computer?
To log-in to ROAM's clientless portal, you need a computer running any popular operating system (Windows, Macintosh and Linux), and a standard Web browser.
Does a clientless remote access solution require users to access from a specific location?
The ROAM clientless portal can be accessed from any place that has access to the Internet.
Can the ROAM clientless portal work with a Macintosh computer?
Access is clientless for Macintosh computers, including access to Windows-based applications.
|
| |
