configure AWS resources - API clients #328
Labels
complexity: medium
Straightforward but some complexity (e.g., involves multiple files); will take 2-6 hours
dependency
Issue has dependencies
feature: infrastructure
For changes on site technical architecture
role: dev ops
s: PD team
stakeholder: People Depot Team
size: 2pt
Can be done in 7-12 hours
Milestone
Dependency
Overview
As part of our AWS configuration, we need to work with #ops to configure API clients.
Action Items
client secret
client secret
for PD admin siteAfter Merge
Resources/Instructions
requirements:
we need at least one API client configured. We may need to set up
client with no secret for PD backend
for now for logging in to the backend admin site using cognito, unless we get the authentication working with the client secret by the time this issue is being worked on.we would like to use
client secret
-enabled clients so we can track where the users are logging in from (from which app). Cognito client secrets - API client #174each API client app (such as VRMS, website, CTJ, PD admin site) should have its own API client "config" associated with the user pool
for quick reference: configs for API clients currently associated with the VRMS testing user pool
client which returns the auth token in the url for manual testing
******
client with no secret for PD backend (need to fix later)
client with secret for client with backend
******
see the actual API clients in AWS for any configs missing here
The text was updated successfully, but these errors were encountered: