-
Notifications
You must be signed in to change notification settings - Fork 456
Enable Google KMS and Azure Key Vault for publisher login tool #696
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
Enable Google KMS and Azure Key Vault for publisher login tool #696
Conversation
4daf89b to
60001e6
Compare
Design doc is in this issue comment: modelcontextprotocol#482 (comment)
60001e6 to
314f336
Compare
Add key length check # Conflicts: # cmd/publisher/auth/common.go
|
@rdimitrov - thanks for fixing |
|
@domdomegg, @toby - this PR is ready for review! Once this is in Microsoft will be able to publish to the MCP Registry :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, happy to merge
Co-authored-by: adam jones <domdomegg+git@gmail.com>
Co-authored-by: adam jones <domdomegg+git@gmail.com>
Co-authored-by: adam jones <domdomegg+git@gmail.com>
Co-authored-by: adam jones <domdomegg+git@gmail.com>
Motivation and Context
This allows the private key used for DNS or HTTP based authentication to be stored securely in a cloud key management system. These services often provide HSM storage which makes it very hard to leak the private key.
The full context is described in my design document here:
#482 (comment)
How Has This Been Tested?
I have tested it against PROD using an Ed25519 key stored in Google KMS. I have added unit tests. I have tested both ECDSA P-384 and Ed25519 with Az KV and Google KMS against a locally running server.
Breaking Changes
None intended.
Types of changes
Checklist
Additional context