Open tariqhossain opened 2 months ago
From the team: We do have a working solution, but it was complex with a lot of moving parts. Having a private AWS CA would have simplified things and will do so for things like renewals and revocations. So its not something that is time critical now, but it would be useful going forward and useful for other teams on the cloud platform should they have a need to provide mTLS certs. (edited)
This is something we would potentially get as standard if we move CP accounts to MP.
Background
Proposed user journey
Our application would generate its own application key and CSR
The CA would sign it and send an application certificate
CA would send the the CA certificate to our application for us to store in their trust store
The 3rd party application would generate its own application key and CSR
The CA would sign it and send an application certificate back to them
CA would send the the CA certificate to 3rd party for them to store in their trust store
our application/3rd party application can use mTLS to send/receive data
we are expecting the CA to manage rotation and renewal of certificates
Approach
Which part of the user docs does this impact
???
Communicate changes
???
Questions / Assumptions
???
Definition of done
???
Reference
How to write good user stories