You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: Implement certificate display modes (hash, obfuscate) for atomic conversion
ISSUE RESOLVED: Step 5 Certificate Display Mode now correctly affects output
The certificate display modes were previously being ignored in the atomic
conversion process, always showing base64 data regardless of selection.
Changes Made:
1. Enhanced processEapConfigFromBuffer() to apply certificate handling
2. Enhanced processPlistFromBuffer() to apply certificate handling
3. Enhanced processYamlFromBuffer() to apply certificate handling
4. Updated function signatures to include certHandling parameter
5. Applied certService.processCertificatesInObject() in all atomic conversion paths
Certificate Display Modes:
✅ PRESERVE: Shows original base64 certificate data
✅ HASH: Shows cert:sha256:hash... with metadata
✅ OBFUSCATE: Shows [CERTIFICATE DATA REDACTED] with metadata
Test Results:
- 100% success rate across all 108 test combinations
- Enhanced test suite validates certificate modes work correctly
- Manual verification confirms distinct outputs for each mode
- All file types (.mobileconfig, .eap-config, .yaml, .xml) supported
The certificate handling now works consistently across all conversion
paths and file types, providing proper security options for sensitive
certificate data in production environments.
0 commit comments