MID Server FIPS mode configuration is not preserved through auto-upgrades<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue FIPS mode settings on the MID Server are not preserved when the MID Server is auto-upgraded. After an upgrade, FIPS mode must be manually re-enabled. Symptoms MID Server was configured for FIPS compliance before upgradeAfter auto-upgrade, FIPS mode is disabledSecurity compliance checks fail post-upgradeWrapper configuration changes overwritten during upgrade Cause During auto-upgrade, wrapper configuration files and JVM security settings may be overwritten or reset to defaults. FIPS mode requires specific JVM security provider configurations that are not part of the standard upgrade preservation logic. Resolution After every MID Server upgrade, verify FIPS mode is still enabledDocument your FIPS configuration settings before upgradingRe-apply FIPS settings to wrapper-override.conf after each upgradeConsider scripting the FIPS re-enablement as a post-upgrade stepTest MID Server upgrades in sub-production first to verify FIPS settings