B 17159 okta secret management

[danieljordan-caci]

B-17159

Summary

Updated .envrc with Okta client IDs, secrets, and okta tenant URL (secrets & tenant URL in chamber) for local dev environment that serves:
milmovelocal:3000/
officelocal:3000/
adminlocal:3000/

Followed these instructions in Confluence to manage secrets: https://dp3.atlassian.net/wiki/spaces/MT/pages/1249542242/0030+How+to+Manage+Secrets+with+Chamber

Setup to Run the Code

NOTE: if you are getting AWS_PROFILE: unbound variable, try running export AWS_PROFILE=transcom-gov-dev

1. Run make client_run and make server_run in separate terminals
2. Sign in as either customer/office/admin & accept terms
3. You will be redirected to Okta login
4. Sign in or sign up
5. You will be redirected back to MilMove (currently getting Internal Server Error due to incomplete session management), but this does verify proper management of secrets and client ids for each MilMove application.

How to test

Automated testing is currently on hold until remaining login features are implemented

• In order to test the changes, you will need to have access to aws-chamber and run chamber list app-devlocal in your terminal to see the listed secrets.
• To read each secret:
  chamber read app-devlocal okta-customer-secret-key
chamber read app-devlocal okta-office-secret-key
chamber read app-devlocal okta-admin-secret-key

Backend

• Code follows the guidelines for Logging.

[cameroncaci]

Works locally and provides support needed for better refactoring