-
Notifications
You must be signed in to change notification settings - Fork 0
Phase 3: Runtime storage migration (IntuneManager → Intune.Commander) #50
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
270ca3a
feat(phase3): runtime migration from IntuneManager to Intune.Commande…
adamgell b8d963a
Initial plan
Copilot 987d56b
fix: address review comments — CryptographicException catch, using va…
Copilot f491262
Merge pull request #51 from adamgell/copilot/sub-pr-50
adamgell File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -60,6 +60,30 @@ public void Decrypt_InvalidData_Throws() | |
| { | ||
| Assert.ThrowsAny<Exception>(() => _encryption.Decrypt("not-valid-encrypted-data")); | ||
| } | ||
|
|
||
| [Fact] | ||
| public void Decrypt_LegacyPurpose_SucceedsViaFallback() | ||
| { | ||
| // Simulate data that was encrypted before the rename using the legacy purpose string. | ||
| // The service must fall back to "IntuneManager.Profiles.v1" and decrypt it successfully. | ||
| var services = new Microsoft.Extensions.DependencyInjection.ServiceCollection(); | ||
| services.AddDataProtection() | ||
| .SetApplicationName("IntuneManager-Tests") | ||
| .PersistKeysToFileSystem(new DirectoryInfo(_keysDir)); | ||
| using var sp = services.BuildServiceProvider(); | ||
| var provider = sp.GetRequiredService<Microsoft.AspNetCore.DataProtection.IDataProtectionProvider>(); | ||
|
|
||
| // Encrypt directly under the legacy purpose (bypassing ProfileEncryptionService.Encrypt) | ||
| var legacyProtector = provider.CreateProtector("IntuneManager.Profiles.v1"); | ||
| var plainText = "{\"profiles\":[],\"activeProfileId\":null}"; | ||
| var legacyEncrypted = legacyProtector.Protect(plainText); | ||
|
|
||
| // The service (which normally uses "Intune.Commander.Profiles.v1") must fall back | ||
| // and successfully decrypt the legacy-purpose ciphertext. | ||
| var decrypted = _encryption.Decrypt(legacyEncrypted); | ||
|
|
||
| Assert.Equal(plainText, decrypted); | ||
| } | ||
|
Comment on lines
+69
to
+86
|
||
| } | ||
|
|
||
| public class EncryptedProfileServiceTests : IDisposable | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Decrypt() currently catches all exceptions from Unprotect() and falls back to the legacy protector. It would be safer to only fall back on the expected cryptographic failure (e.g., CryptographicException) so unrelated issues (like argument/DI errors) aren’t accidentally masked by the fallback path.