When a deployment is being executed, there may be some value in providing access to account credentials that have already been stored and managed in Octopus Deploy.

While the primary motivating factor for creating the accounts section has been to provide access to deployment targets, some users may get value from using them to access or control other parts of their deployment process that sit behind some authentication mechanism. This would allow OD to better manage all the resources needed to fully complete a deployment with authentication details being securely managed in one place.

The biggest concern with this approach would be ensuring that the credentials remain secure and not be vulnerable to inappropriate disclosure at the wrong time or to the wrong people. To this end, I would also expect that OD should not become seen as purely an authentication storage system and any such feature as described above should be built with the intention of aiding in the deployment process.

This post aims to gather feedback from the community on whether this is a good idea to consider, and if so, any suggestions on what functionality it should provide.