Set up Keys

[kellylein]

In preparation of using the new LH APIs (via the VA.gov team's vets-api integrations) we should get all the client ids and RSA keys we need so we can get them in AWS and devops. This includes requesting credentials from LH for the new APIs (that are ready so far).

• request Lighthouse credentials for the following APIs (they should give us one set of credentials with access to all of these)
  • Benefits Claims API
  • VA Letter Generator API
  • Direct Deposit Management API
  • Benefits Documents API
• Store the credentials in the appropriate spot(s)

[kpethtel]

Conversations with other teams about how to use their services.
Benefits claims:
https://dsva.slack.com/archives/C04KHCT3ZMY/p1679075602837299
Direct deposit:
https://dsva.slack.com/archives/C03P6C3FYMR/p1679424568612719
Disability ratings:
https://dsva.slack.com/archives/C04KW0B46N5/p1679435500278029

[kpethtel]

Handing this over to Andrew because I'm going to be OOO. Here's the current status.

The vets-api PR (department-of-veterans-affairs/vets-api#12172) is approved by i can’t get it through CI after several tried.

I created a manifests branch (4743-mobile-lighthouse-api-keys) that’s mostly complete. the small issue is that the name MOBILE_LIGHTHOUSE_KEY_PATH was already in use. andrew intends to remove the existing use. once it's gone, we should finish this using the names we want to use.

i have a devops branch (also 4743-mobile-lighthouse-api-keys) that i believe is ready.

this also doesn’t include production keys so we’ll need a second ticket for doing this for prod, but it should be far simpler because we know exactly what we need to do.