AWS change SSH keys; install & configure WSO2 Open Banking

1. Change the SSH keys in AWS for 6 servers. Set up the owner with the global key and issue keys for each server. Owner can issue/control access to each server to each developer and can withdraw access to the server without changing the SSH key. 2. WSO2 Open Banking. https://docs.wso2.com/display/OB140/Deployment+Guide. This is built using J2EE. Open Banking consist of several pre-integrated servers. Install, configure and test all requested features. 1. Install Open Banking into separate servers (1 per component) according to the documentation 2. Configure so that our front and back end code can call the API's for A. User set up - username and password. B. Select security questions from the available bank of questions or we can edit/add our own. Store the answers C. Allow user to create their own 'Secret question' and provide the answer. Store both items D. Store all information in an encrypted manner. E. During authentication, front end and back end will communicate with Open Banking. Use twice hashed values only, never the actual username or password. F. Provide key to the front and back end for session handling 3. Configure the API Manager with Analytics (part of Open Banking) so that: A. The front end API's communicate with the back end API's through the authentication, encryption and monitoring features of API Manager. B. Expose the interfaces/API's that the front and back end API's have to call 4. Expose the transactions monitoring API's of Open banking for our front and back end API's to pass transaction information to Open Banking for storage, analysis and monitoring. A. The schema is described in the Open Banking documentation B. We don't need the transactions monitoring API's to connect with outside 3rd party API's, only our front and back end API's. So we don't need to test with WSO2's testing service