Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Credential Manager as Secret Store Option #150

Open
GarthJL1965 opened this issue Jun 24, 2020 · 3 comments
Open

Windows Credential Manager as Secret Store Option #150

GarthJL1965 opened this issue Jun 24, 2020 · 3 comments
Assignees
Labels
secret-provider All issues related to secret providers secret-store All issues related to our secret store
Projects

Comments

@GarthJL1965
Copy link

What secret store are you interested in?

I'm very interested in using the Windows Credential Manager as a Secret Store Provider/Option - I successfully campaigned for this and used it at my last place of work - for C# Win32 Services in particular. I think we need to stipulate, we're talking about Windows XP+ here. A Seperate version could be made available for *nix, Mac 'KeyStores'

What scenarios would it enable you?

  1. A person who has access to the 'secret' can set it up on the deployment server using the a) standard Windows Credential Manager or b) a Utility with a pop-up GUI - in this situation the roles of developer/installer are divided

  2. The Service/Application can have the code to create the required Secret in the Windows Credentials 'Store' built in (much as per (b) from point 1, called at (example) Service installation time - as per (1), the secret need not be made available to the Developer, if roles/responsibilities etc are different (the lines in DevOps, DevSecOps blur some of this now)

More information
Because my previous code was 'commercial', I would need to re-do it for this - I'm happy to write & test the code, using C# & Win32 Interop

@GarthJL1965 GarthJL1965 added secret-provider All issues related to secret providers secret-store All issues related to our secret store labels Jun 24, 2020
@tomkerkhove
Copy link
Contributor

Great to hear, are you open for contributing this?

@GarthJL1965
Copy link
Author

@tomkerkhove yes, I can contribute - I've found https://security.arcus-azure.net/features/secret-store/create-new-secret-provider. I'll get my head around the repo, code style, error handling etc in the next day or so

@tomkerkhove
Copy link
Contributor

Sounds good, thanks!

@stijnmoreels stijnmoreels added this to To do in Roadmap via automation Jan 19, 2021
@stijnmoreels stijnmoreels moved this from To do to In Development in Roadmap Jan 19, 2021
@stijnmoreels stijnmoreels added this to the v1.5.0 milestone Jan 19, 2021
@tomkerkhove tomkerkhove removed this from the v1.5.0 milestone Feb 16, 2021
@tomkerkhove tomkerkhove moved this from In Development to To do in Roadmap Feb 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
secret-provider All issues related to secret providers secret-store All issues related to our secret store
Projects
Roadmap
  
To do
Development

No branches or pull requests

3 participants