search

CodingBash / katie-soi-era

Event Registration Application for the Katie School of Insurance of Illinois State University
0 stars 0 forks source link

Securely add authorization on using Loudcloud through the REST Template #79

Closed CodingBash closed 8 years ago

CodingBash commented 8 years ago

Story: #16

CodingBash commented 8 years ago

Refererence: http://www.baeldung.com/2012/04/16/how-to-use-resttemplate-with-basic-authentication-in-spring-3-1/

CodingBash commented 8 years ago

@rishikanths @Epilp25 Need to find a way to store the Loudcloud credentials securely. Two options (that I know of, offer any other solutions that you know): 1) Keep the credentials stored on the server storage .properties file and extract it if user is authorized. PROS: Easy to develop. CONS: All developers able to see .properties file, if not .gitignored/cautious the credentials will appear on GitHub. If Loudcloud credentials change, the .properties file will need to be updated so project would need to be rebuild/deployed.

2) Keep the credentials on a remote server and remotely extract it if user is authorized. PROS: If Loudcloud credentials change, the remote server file would need to be updated but the project would not have to be redeployed. Credentials don't appear in project files. CONS: Harder to implement. Not sure but I potentially may need ANOTHER credential to connect to the remote server which would be redundant.

Would we be able to do option 1 without a huge impact (storing on project files doesn't matter, password won't change that often)? Also, may need to do more research on other solutions to this problem. If you guys know of other solutions, please offer. We can discuss this in our next meeting.

-Bash

CodingBash commented 8 years ago

@rishikanths @Epilp25 This task is also keeping me from working on any tasks dealing with the Loudcloud REST calls such as #78 #72 #71 (since can't access it from app yet), so this will need to be high priority to figure this out.