How is encryption supported?

There are many ways in which encryption is supported.

The application supports encryption for the following places:

Properties that are specified in the yfs.properties, yifclient.properties, and management.properties files
Credit card numbers

Encryption through yfs.properties

Properties such as the JDBC URL, database User ID, and Password can be stored encrypted in the customer_overrides.properties file. Because the application needs this information to connect to the database, these values must be decrypted by the application. If you do not want the application to ever decrypt data, these properties cannot be stored encrypted.

Note: If you want set any of the properties that are specified in the yfs.properties file, add an entry for that particular property in the <runtime_sandbox>/properties/customer_overrides.properties file.

Encryption for credit card numbers

The application can encrypt credit card numbers before it stores them in the database. Unlike the properties that are specified in the yfs.properties file, decrypted credit card numbers are never required by the application for default processing. However, you can extend the application by implementing a user exit that requires decrypted credit card numbers for charging or storing user preferences. If you don't want the application to decrypt information automatically, you must decrypt these credit card numbers in your implementation of the user exit.