Mastercard International Incorporated

Douglas Paul Forguson

Weihua Zhou

Uday Kumar Survi

Srinivas M Gummididala

Steven Delles

Sachin Kumar Rathore

Systems and methods of centralized, global secure shell (SSH) key administration and management are provided, where a secure file transfer protocol (SFTP) application programming interface (API) can be leveraged to integrate centralized SSH key administration across any and all SFTP API or other file transfer installations. This allows an administrative entity to use a central server, for example, to perform client and server SSH key administration and management (e.g., SSH key creation, removal, distribution, and expiration reporting/tracking), scheduling, configuration updates, and the like across an unlimited number of file transfer installations and platforms (and therefore, is also scalable). A single management interface can be utilized for viewing and updating SSH keys for applications, and SSH keys can be propagated to application servers where the SSH keys can be activated based on a scheduled time.

Secure shell file transfer protocol key administration

An application having an application architecture including an application programming interface (API) client capable of automatically retrieving a passphrase from a secure passphrase vault based on a user authentication ID used to access the application is provided. The passphrase is used to access a secure file transfer protocol (SFTP) authentication key via an API server communicatively connected to the API client. The SFTP authentication key is used to authenticate an SFTP file transfer request from the application to an intended file recipient.

Secure file transfer with secure SSH key authentication

An operationally monolithic application is provided, where the application resides in a first program address space of an application server. The application calls to an application component residing in a second program address space of the application server, the application component being built upon a framework of the operationally monolithic application. The operationally monolithic application loads at least a first library upon which it depends to invoke a first method, and the application component loads at least a second library upon which it depends to invoke a second method. The first and second libraries can co-exist on the application server despite being different versions of the same libraries.

Growing community of inventors

Richmond Heights, MO, United States of America

Douglas Paul Forguson