Dear Team,
With the introduction of the mandatory three-month DB wallet rotation for FDI users, there has been an increased operational effort required to manage wallet updates. Within FDI, we have several ADW database connections, some private and others shared. As the existing connections become invalid after wallet rotation, the Operations team currently needs to update and communicate the new wallet across multiple connections and FDI environments every three months.
While an SOP has been prepared and the team is also working on automation, I wanted to check whether there could be an option to centrally manage DB wallets within FDI.
For example, when creating an ADW database connection, users could either:
- Provide/upload the wallet and connection details directly, as they do today; or
- Reference a centrally uploaded DB wallet through a pointer/reference.
The second option would allow multiple ADW connections to reference the same centrally managed wallet rather than having a separate wallet uploaded for each connection.
With such an approach, following a wallet rotation, the Operations team would only need to replace the wallet in one central location. All connections referencing that wallet could then automatically use the updated wallet, avoiding the need to update multiple individual connections every three months.
Could you please advise whether such a centralized wallet management/reference capability is currently available or could be considered as an enhancement for FDI?
Regards,
Bhavin Desai
