Data Loss Prevention

 View Only
  • 1.  Active Directory Login is Unavailable After Upgrade to Data Loss Prevention 15.5 MP1

    Posted Apr 19, 2019 10:32 AM

    It looks like a regression bug like what was in 15.0 to 15.0 MP1  when it replaced the Kerberos Authentication “springSecurityContext.xml” with the default forms based template (REF https://support.symantec.com/en_US/article.TECH248556.embed.html ).

     

    If you have not started this update, then make sure you backup the following folder in addition to best practice EnforceReinstallationResources.zip etc. \Program Files\Symantec\DataLossPrevention\EnforceServer\15.5\Protect\tomcat\webapps\ProtectManager\WEB-INF

     

    However, if you did not backup this file previously (since the MP patches no longer do their own auto-archive of the directory structure), you will need to perorm the following to be able to log in with AD Authenticated accounts again:

    1. Go into the following folder: \Program Files\Symantec\DataLossPrevention\EnforceServer\15.5\Protect\tomcat\webapps\ProtectManager\security\template
    2. Grab and edit springSecurityContext-Kerberos.xml
    3. Replace <property name=”krbConfLocation” value=”C:\SymantecDLP\Protect\config\krb5.ini”/> with the current location of your krb5.ini file (presumably \Program Files\Symantec\DataLossPrevention\EnforceServer\15.5\Protect\config\krb5.ini)
    4. Rename springSecurityContext-Kerberos.xml to springSecurityContext.xml
    5. Copy and overwrite the file in the following folder: \Program Files\Symantec\DataLossPrevention\EnforceServer\15.5\Protect\tomcat\webapps\ProtectManager\WEB-INF
    6. Restart SymantecDLPManagerService


  • 2.  RE: Active Directory Login is Unavailable After Upgrade to Data Loss Prevention 15.5 MP1

    Posted Apr 22, 2019 01:01 PM

    Great. Thanks for the tip as we're about to apply the MP.  How did, or did you, uninstall the indexer?



  • 3.  RE: Active Directory Login is Unavailable After Upgrade to Data Loss Prevention 15.5 MP1

    Posted Jun 04, 2019 11:03 AM

    You're welcome.  We did not deploy an external Indexer, so this step was not a factor.