| |
|
|
| |
|
|
| |
|
|
| |
| Quotes |
"Weeks and weeks go by without me ever seeing a service problem"
Henrik Jensen, IT Specialist, Vaekstfonden
|
| |
|
|
|
|
G/On 5 introduces a new, more flexible and diverse client concept. In addition to supporting different operating system platforms, the G/On 5 Client will be able to support a wide range of authentication tokens. These tokens vary significantly in functionality and capabilities and G/On 5 provides different client options offering customers the benefit of the various features and price points. For instance, one of the options is a variety of tokens which offer smart card functionality combined with or integrated with other functionality. Most are USB based tokens combined with memory for software storage and CD-ROM and some of them have integrated hardware encryption and additional smart card readers. Future plans for G/On 5 include support for more traditional tokens such as the RSA token, SMS-based tokens, and other One Time Password (OTP) devices.
G/On 5’s new, flexible plug-in architecture is designed to support these and future new and innovative authentication tokens. Over time, this will enable the development of add-ons for specialized solutions incorporating features and functions of different tokens and token-based solutions. One example is the creation of completely integrated G/On based solutions for physical access (door access control) and virtual access (IT access) based on smart card and contactless tokens.
In addition to the authentication itself, all G/On token options are based upon the core G/On Client that handles the encrypted virtual connection to the G/On Gateway Server. Technically speaking, the G/On Client is a port forwarding proxy that captures data from an application client on a user’s PC and forwards the traffic to the encrypted (and otherwise protected) connection to its corresponding G/On Gateway Server. The TCP connections from the G/On Client terminates on the G/On Gateway Server that in turns forwards the traffic to the correct application server. The application client (e.g. local Outlook, a Remote Desktop (RDP) client or any other client of a client/server solution) effectively sees its corresponding application server as if it was co-located on the user PC. The connection created, controlled and protected by G/On is kept transparent to the communication between the application client and the application server.
The functionality of the G/On Client implements the client side support for:
- Authentication and Authorization: as controlled by the G/On Server and depending upon the supported list of authentication client options
- Launch and Traffic: launching the authorized application clients as outlined above and transporting the traffic between application client and network
- User Dialog: for login and presenting the result of the authorization to the end user controlling what and how the user is allowed to access applications
- Deployment of local software on the user device as requested by user or the G/On Server.
The G/On Client is thus an “extension” of the G/On Gateway Server implementing and enforcing the decisions made by the server. It is also the G/On Client that manages the actual user dialog and adapts the dialog to the device (e.g. OS) the user is running from.
The G/On user dialog component supports the user with activity indicators and different warning or notification screens, presenting the results of the final authorization decisions in the form of user specific menus and finally accepting and acting upon user selection of menu items. As with all client side functionality, configuration and setup of user dialog is controlled entirely by the G/On Server.
|
|
|
| |
|
|
Copyright © Giritech. All rights reserved.
|
