Vault encryption abstraction framework system
A vault encryption abstraction framework computing system provides interface functionality to facilitate integration of client applications with vaulting solutions. The vault encryption abstraction framework manages custom authentication and authorization using the vaulting solution application for one or more client applications such as by periodically rotating or renewing any authentication tokens. The vault encryption abstraction framework includes a scheduler to manage timing requirements and to configure the client application to the schedule by setting the renewed token value to an API endpoint (e.g., a function return) and/or a configuration file for access by one or more client applications. This event triggers the client application to update to the latest token value. The vault encryption abstraction framework then triggers the vaulting solution to create and return the new key. The new key is then returned to the client application. A history of the key generation messages and subsequent status is saved in a data log.
1. A method comprising:
receiving, via an application interface by an abstraction framework and from an application, an electronic command request to update an electronic security token, wherein the request is in a first format;
triggering, by the abstraction framework and based on the electronic command, generation of the electronic security token by a vaulting application;
receiving, via a vault interface and from the vaulting application, a response message comprising the electronic security token, wherein the response message is in a second format; and
communicating, via the application interface and via a network by the abstraction framework, a second response message comprising the electronic security token, wherein the second response message is in the first format.
2. The method of claim 1 , comprising:
configuring, via a configuration file, a scheduler of the abstraction framework via a configuration file; and
triggering, based on a scheduling event triggered by the scheduler, the application to request an update to the electronic security token.
3. The method of claim 1 , wherein the first format comprises a configuration file and the second format comprises an application programming interface function.
4. The method of claim 1 , wherein the first format comprises a first application programming interface function and the second format comprises a second application interface function, wherein the first application programming interface function is incompatible with the second application programming interface function.
5. The method of claim 1 , comprising:
storing, by the abstraction framework, information about the request received from the application and the response from the vaulting application.
6. A system comprising:
a first computing device processing instructions to provide functionality via a first application;
a vault computing device processing instructions to provide data vault and encryption services; and
a framework computing device comprising:
a processor; and
non-transitory memory storing instructions that, when executed by a processor, cause the framework computing device to:
receive, via an application interface by an abstraction framework and from the first computing device, an electronic command request from the application to update an electronic security token, wherein the request is in a first format;
trigger, by the abstraction framework and based on the electronic command, generation of the electronic security token by the vault computing device;
receive, via a vault interface and from the vault computing device, a response message comprising the electronic security token, wherein the response message is in a second format; and
send, via the application interface and via a network by the abstraction framework to the first computing device, a second response message comprising the electronic security token, wherein the second response message is in the first format.
7. The system of claim 6 , wherein the instructions further cause the framework computing device to:
configure, via a configuration file, a scheduler of the abstraction framework via a configuration file; and
initiate, based on a scheduling event at the first computing device triggered by the scheduler, the first application to communicate a request to update to the electronic security token.
8. The system of claim 7 , wherein the instructions further cause the framework computing device to send, by the scheduler via the network, the scheduling event to the first computing device.
9. The system of claim 8 , wherein the scheduling event is generated by the framework computing device and pushed to the first computing device.
10. The system of claim 6 , wherein the first format comprises a configuration file and the second format comprises an application programming interface function.
11. The system of claim 6 , wherein the first format comprises a first application programming interface function and the second format comprises a second application interface function, wherein the first application programming interface function is incompatible with the second application programming interface function.
12. The system of claim 6 , wherein the instructions further cause the framework computing device to store, by the abstraction framework, information about the request received from the application and the response from the vault computing device.
13. Non-transitory computer readable media storing instructions, that when executed by a processor, cause a computing device to:
receive, via an application interface by an abstraction framework and from a first computing device, an electronic command request from an application to update an electronic security token, wherein the request is in a first format;
trigger, by the abstraction framework and based on the electronic command, generation of the electronic security token by a vault computing device;
receive, via a vault interface and from the vault computing device, a response message comprising the electronic security token, wherein the response message is in a second format; and
send, via the application interface and via a network by the abstraction framework to the first computing device, a second response message comprising the electronic security token, wherein the second response message is in the first format.
14. The computer readable media of claim 13 , wherein the instructions further cause the computing device to:
configure, via a configuration file, a scheduler of the abstraction framework via a configuration file; and
initiate, based on a scheduling event at the first computing device triggered by the scheduler, the application to communicate a request to update to the electronic security token.
15. The computer readable media of claim 14 , wherein the instructions further cause the computing device to send, by the scheduler via the network, the scheduling event to the first computing device.
16. The computer readable media of claim 14 , wherein the scheduling event is generated by the framework computing device and pushed to the first computing device.
17. The computer readable media of claim 13 , wherein the first format comprises a configuration file and the second format comprises an application programming interface function.
18. The computer readable media of claim 13 , wherein the first format comprises a first application programming interface function and the second format comprises a second application interface function, wherein the first application programming interface function is incompatible with the second application programming interface function.
19. The computer readable media of claim 13 , wherein the instructions further cause the framework computing device to store, by the abstraction framework, information about the request received from the application and the response from the vault computing device.