UniPay Directory Structure
Top Level Resources:
| Name | Type | Description |
|---|---|---|
| $app-home | Virtual | Root folder for UniPay installation |
| $ftpgates-root | Virtual | Root folder for FTP Gates's batch service. All file exchanges occur through this folder.
Files to be sent to Providers are placed in respective sub-folders and are subsequently processed by UniBroker or by UniPay. Tokenization results are placed in respective sub-folder by UniBroker for further consumption by UniPay. |
| $profiles-home | Virtual | Stores build profiles and associated resources necessary for the application deployment. |
| $sources-home | Virtual | Root directory for the repository with the source code (currently GIT). |
| $telium2-root | Virtual | Root directory for the entire file structure inside the terminal from the Tellium2 family. This directory can contain 5 applications. |
| $unibroker-home | Virtual | Root folder for UniBroker installation |
| $unibroker-root | Virtual | Root folder for UniBroker's batch service. All file exchanges occur through this folder.
Files to be sent to Providers are placed in respective sub-folders and are subsequently processed by UniBroker. Results are placed by respective sub-folders by UniBroker for further consumption by UniPay. |
Resource Types:
| Directory | physical directory on server's hard drive |
| File | physical file on server's hard drive |
| Virtual | virtual directory, which maps to a physical directory, name and location of which are determined by the deployment conditions and requirements |
key.txt
($app-home/resources/key.txt)
Stores master key used for internal application encryption. Internal encryption may be used when tokenization is not available to store credit card numbers (this approach is not PCI compliant). Internal encryption is also used to encrypt password and other sensitive information within the application.
The file must contain a single value (no carriage returns or unnecessary spaces) that is to be used as the key.
Normally, the key gets auto-generated by the system during the setup process. Note that for security purposes, the file doesn't actually contain the encryption key, but an altered version of it.
Altering the key or replacing it with a value that was not prepared following system's algorithm will cause malfunction of the encryption process. Using the key to decrypt values in the database will not produce any meaningful results. An attempt to extract the key through a direct decryption of the value in the file is not likely to produce any meaningful results either.
Warning: loss/damage of the key will result in a complete loss of all encrypted data. Always keep a backup copy of the key.
The file must contain a single value (no carriage returns or unnecessary spaces) that is to be used as the key.
Normally, the key gets auto-generated by the system during the setup process. Note that for security purposes, the file doesn't actually contain the encryption key, but an altered version of it.
Altering the key or replacing it with a value that was not prepared following system's algorithm will cause malfunction of the encryption process. Using the key to decrypt values in the database will not produce any meaningful results. An attempt to extract the key through a direct decryption of the value in the file is not likely to produce any meaningful results either.
Warning: loss/damage of the key will result in a complete loss of all encrypted data. Always keep a backup copy of the key.
Copyright ©
Constellation Payments. All Rights Reserved.
All Logos and Trademarks used or mentioned on this page are copyrighted property of their respective owners and are used for display purposes only.