Update sample5.cmd to match test results #1091
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://learn.microsoft.com/iis/manage/configuring-security/using-encryption-to-protect-passwords
Based on the source code of
createProvider.exe
showed in this article, when its input isiisWasKey RsaKeyForWAS Rsa_WAS
, it should add a provider inmachine.config
whose name isRsa_WAS
, with keyContainerNameiisWasKey
and descriptionRsaKeyForWAS
. However, the element in the old sample file didn't match.Besides, the sample file should have showed enough context of all three provider items, so I chose to expand the contents to the entire
configProtectedData
tag. In this way, thedefaultProvider
attribute modified bysetProvider.exe
is also showed.What this pull request doesn't include is the hint that how x86/x64 and .NET Framework 4.0+ scenarios should be handled, because the original article was only written with .NET Framework 2.0 and x86 in mind, but I assume the audience of this article is very small and should be capable enough.
@Rick-Anderson