 Documentación técnica de Sage 50 (50.7800) |
|
Documentación técnica de Sage 50 (50.7800) |
|
Key storage implementation for persistent reading/writing signing key. Más...
Métodos públicos | |
| BcEsKeyStorage () | |
| Constructor of BcEsKeyStorage without parameters. Only for test purposes ! Más... | |
| BcEsKeyStorage (dynamic objKeyStorProductApp, ILogger bcEsLogger=null) | |
| Constructor with key storage product app object and logger object, for test and production purposes, both. Más... | |
| string | ReadKey () |
| Read the signingkey from the key storage used. Más... | |
| void | WriteKey (string key) |
| Write the signingkey from the key storage used. Más... | |
Key storage implementation for persistent reading/writing signing key.
Is responsability of the final product (Sage50/Sage200 Spain) supply a dynamic object with two methods ReadKey() and WriteKey() in which read/write the signing key from/to a unique shared ubication for all users that work with the product application.
This parameters are received in the constructor, if the constructor receive no parameters BcEsKeyStorage uses a no persistent mechanism TestKeyFileStorage which read/write the signing key in a local file which are not shared by all the users. In production mode create BcKeyStorage always with the objKeyStorageProductApp parameter !!
Definición en la línea 18 del archivo BcKeyStorage.cs.
|
inline |
Constructor of BcEsKeyStorage without parameters. Only for test purposes !
In this case the BcEsKeyStorage class behaviour like the TestFileKeyStorage class which work reading/saving the key into a ASCII file in the AppDomain.CurrentDomain.BaseDirectory directory. Only for test purposes. In production mode never would be called this constructor without parameters !! In production mode use always the BcEsKeyStorage(dynamic objKeyStorProductApp, ILogger bcEsLogger) constructor with the objKeyStorProductApp declared.
In this case the logger behaviour is like Sage.BankingCloud.Client.Default.DefaultLogger() which work with console.
Definición en la línea 67 del archivo BcKeyStorage.cs.
|
inline |
Constructor with key storage product app object and logger object, for test and production purposes, both.
| objKeyStorProductApp | Key storage product app object supplied by the product application, must have 2 methods called ReadKey() and WriteKey(). |
| bcEsLogger | Logger produc app for logging. If not received BcEsKeyStorage uses a DefaultLogger mechanism which work with the console. |
Definición en la línea 80 del archivo BcKeyStorage.cs.
|
inline |
Read the signingkey from the key storage used.
If product app storage key object supplied in the constructor, read the signing key from it (valid for TEST and PROD mode) If no product app storage key object supplied, uses a ASCII local file storage mechanism (TestFileKeyStorage, only for TEST mode).
In PRODUCTION mode is responsability of the final product (Sage50/Sage200 Spain) supply this object with two methods ReadKey() and WriteKey() which read/write the signing key from/to a unique shared ubication for all users that are working with the product app.
Definición en la línea 110 del archivo BcKeyStorage.cs.
|
inline |
Write the signingkey from the key storage used.
If product app storage key object supplied in the constructor, write the signing key to it (valid for TEST and PROD mode). If no product app storage key object supplied, uses a ASCII local file storage mechanism (TestFileKeyStorage, only for TEST mode).
In PRODUCTION mode is responsability of the final product (Sage50/Sage200 Spain) supply this object with two methods ReadKey() and WriteKey() which read/write the signing key from/to a unique shared ubication for all users that are working with the product app.
Definición en la línea 155 del archivo BcKeyStorage.cs.