For connections in OAC/FDI that require a private API key or private key file (for example, Snowflake key-pair authentication), could we provide an option to retrieve the key directly from a secure secrets management solution rather than requiring users to temporarily save the key locally and upload it through the connection UI?
For example, the current Snowflake connection flow includes a Private API Key field that requires the user to select and upload a private key file.
This creates a security and operational concern for customers who do not want private keys stored temporarily on a local workstation or handled manually during configuration.
A preferred approach would be to support integrations with enterprise secrets management solutions, such as OCI Vault / Secrets or AWS Secrets Manager, where OAC/FDI could retrieve the private key securely when needed.
Ideally, the connection configuration could provide something like:
Private API Key → Retrieve from Secret / Secret Management Service
This would allow customers to reference a securely stored private key rather than upload the key file itself, supporting centralized secret management, rotation, access controls, and auditing.
Currently, the connection UI appears to only support uploading the private key file, with no option to reference a key stored in a secrets management service. Could OAC/FDI support retrieving private keys directly from solutions such as OCI Vault or AWS Secrets Manager instead of requiring a local file upload?
