Skip to content

Conversation

@guardrex
Copy link
Collaborator

@guardrex guardrex commented Oct 25, 2024

Fixes #33933

Notes

  • 🎉 Seems to work well, including during local development in VS.
  • I am adding a bit on the initialization step for the Secret Manager tool. You asked about that before, and I responded that the user secret Id is already there. However, they really should get a unique Id, so I'm adding a bit here to have them run the init command ... and I've already pulled the <UserSecretId> from the sample app on Drop user secrets Id blazor-samples#379. I've already done the same thing for the OIDC-based samples and article on Drop hardcoded user secrets IDs blazor-samples#380 and Initialize the Secret Manger tool #33949.
  • Check my naming of API! You know how badly a green dinosaur 🦖 can name things 🙈😆.

Internal previews

📄 File 🔗 Preview link
aspnetcore/blazor/security/blazor-web-app-with-entra.md aspnetcore/blazor/security/blazor-web-app-with-entra
aspnetcore/grpc/why-migrate-wcf-to-dotnet-grpc.md aspnetcore/grpc/why-migrate-wcf-to-dotnet-grpc

@guardrex guardrex self-assigned this Oct 26, 2024
@guardrex guardrex requested a review from halter73 October 28, 2024 14:43
@guardrex guardrex marked this pull request as ready for review October 28, 2024 14:49
@guardrex guardrex merged commit 50a34f5 into main Nov 19, 2024
3 checks passed
@guardrex guardrex deleted the guardrex/blazor-add-key-vault-code-example branch November 19, 2024 13:36
@guardrex guardrex mentioned this pull request Jan 3, 2025
93 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Key Vault approach for client secret

2 participants