If you have SAP® R/3 and/or SAP® NetWeaver® Web Application Servers deployed in your network, and would like one, or more of the following :

• Improved SAP® system, and network security;
• A SAP® Certified, and Commercially Supported SNC Kerberos Library which can be used for Secure Single SignOn ("SSSO") and Integrated Windows Authentication ("IWA") with SAPgui on Windows and SAP® Applications deployed on Windows, UNIX or Linux Servers;
• A SAP® Certified, and Commercially Supported SNC Kerberos Library which can be used to provide secure communications between SAP® ITS AGate Servers and SAP® Applications deployed on Windows, UNIX or Linux Servers;
• Allow secure SAPrfc connections between SAP® Application Servers;
• A solution which allows IWA and SSSO for users logging onto :
  • SAP® Applications accessible via SAP® Front End software (e.g. SAPlogon, SAPgui, SAPlpd, SAPrfc);
  • SAP® Applications via a Web browser using services on SAP® Internet Transaction Server ("ITS");
  • SAP® Applications hosted on Microsoft .NET servers, and where secure communciations are required between the .NET Application Server and the SAP® Back-End systems;
  • SAP® Enterprise Portal;
  • SAP® Applications via a Web browser, and hosted on SAP® Web Application Server;
  • SAP® Applications implemented as services in the Integrated ITS (e.g. webgui on SAP® NetWeaver® 2004);
• A SAP® Certified, and Powered by SAP® NetWeaver® JAAS Login Module, which uses SPNEGO, GSS-API and Kerberos for user IWA and SSSO;
• A replacement for the SAP® IIS Proxy product, which is being widthdrawn by SAP® AG in January 2006;
• Avoid transmission of passwords across the network between SAP® Application components, or during a user logon session;
• Allow user authentication to use a method of authentication stronger than a user account name and password (e.g. using a smart card, or two-factor token device);
• Support for fall-back authentication, so that when accessing SAP® Applications via a Web browser, and IWA is not possible (e.g. when user is unable to logon to their Workstation using a Microsoft Active Directory Domain user account) an alternative logon method can be implemented. The fall-back method can ask the user to logon using their Microsoft Active Directory Domain user account name and password, but via the browser instead of during their initial Workstation logon;
• Allow user mapping, so that an authenticated identity can be mapped onto a SAP® User ID;
• Implement data privacy, by encrypting network communication sessions between application components, as well as providing data integrity to detect any tampering of data as it is transmitted across the network;
• Centralised user password policy management, and common authentication;
• A strategic authentication solution, which is complementary when used with other SAP® security products, e.g. When used with a SAP® user provisioning product, and/or when SAP® Web Application Server has been configured to use Microsoft Active Directory as a user store.

Then, we have a security solution which will meet your needs. More details on each of the solutions available, is provided below :