Constraints on Using SSF

SSF requires the use of SAP NetWeaver Single Sign-On or a third-party security product to provide its functions. As the default provider, we deliver the SAP Cryptographic Library with SAP NetWeaver AS.

For more information, see SAP Note 1848999 .

For digital envelopes, encryption, or crypto hardware (for example, smart cards or crypto boxes), use an external security product. SAP provides the SAP Cryptographic Library free of charge, or you can use a certified partner product.

For information about supported products, see the SAP-certified partners (http://www.sap.com/softwarepartner).

To effectively use the SSF mechanisms, you must have an established public-key infrastructure (PKI). The PKI makes sure that you can validate and trust the digital signatures, certificates, and Certification Authorities (CAs). A PKI is often, although not necessarily, supported by the external security products that are available on the market. Although SAP NetWeaver AS does not provide a PKI directly, it does support PKIs provided by various security products.

Depending on the security product that you use, you can establish the use of a PKI in one of many ways. You may want to create your own PKI and CA that you link to your customers, or you and your customers may want to agree on a common Trust Center. A common Trust Center is a third-party instance that both you and your customers can trust to validate and authenticate your PKI participants. Using a common Trust Center can solve many of the currently open questions regarding the establishment of a PKI.

There are also laws in various countries that regulate the use of cryptography and digital signatures. These laws are currently controversial and may change. Keep yourself informed on the impact these laws may have on your applications, and make sure that you are aware of any further developments.