nickiannone / personal-showcase Goto Github PK

In order to persist data, the application should have a way to be configured with an external persistence layer, which then gets used for managing creation, reading, updating, and deleting business objects from the persistence layer, as well as serving authentication.

This should contain:

• A way to enter the connection information and credentials for the persistence solution
• Verification of the schema of the persistence solution (ie. which resources are accessible on what paths)
• A way to retrieve a user principal from the persistence solution (ie. logging in and getting permissions)
• A way to securely specify secrets (ie. passwords for the connection and for specific user accounts)

This should be structured as a mapping or implementation of an interface which consumes some externally-configurable set of rules, in the form of a JSON configuration file with key-value pairs. Passwords and other secrets should not be stored in code or in a repository; they must instead point to a separate encrypted keystore structure of some type in order to be isolated from the version control system or application filesystem.