Application
There are a number of "off the shelf" integrations available that allow PINsafe to authenticate users for access to applications.
Integrations with applications tend to use the PINsafe XML-API, which is a flexible, easy to develop against API. Unless otherwise stated all these integrations can be implemented without need to expose the PINsafe server to the internet.
| Application | Notes |
|
Apache Tomcat (J2EE Application) |
Via a servlet filter. Swivel Secure have a generic filter that can be customised as required. For more information contact support@swivelsecure.com |
| Apache HTTP Server | This can be achieved by configuring the server to use RADIUS. See brief overview |
| Arx Co-Sign | Does require PINsafe to be accessible to the internet at this stage. http://www.arx.com Integration guide available |
|
Citrix Presentation Suite 4.5/4.6 |
Integration packs available for 4.5, 4.6, 5.0 and 5.1 |
| Imprivata | Single Sign-On solution, www.imprivata.com. For more information contact support@swivelsecure.com |
| Microsoft IIS | Via IIS (ISAPI) filter. Filter and associated documentation are available as a zip file. |
| Microsoft ISA Server | For Sharepoint and OWA. ISA Filter |
| Microsoft OWA | Possible via ISA filter but also via IIS filter. See web integration guides for details |
| Microsoft Terminal Services |
You can deploy a Terminal Services GINA to secure terminal services access with PINsafe. (Windows Server 2003 and XP) |
| SUN Global Desktop |
This requires configuring SGD to use RADIUS. For more details contact support@swivelsecure.com |
Custom Integrations
The PINsafe Agent-XML API provides a means of creating custom integrations with most enterprise applications.
Integrations is facilitated by a number of examples and clients that can be made available to potential developers.
This includes a Java Client, an ASP.Net client, a PHP Client plus s set of sample .jsp pages.
Contact support@swivelsecure.com if you have any custom integration requirements.