Configuring RSA authentication in Endpoint Protection Manager fails with error which states that sdconf.rec cannot be uploaded
search cancel

Configuring RSA authentication in Endpoint Protection Manager fails with error which states that sdconf.rec cannot be uploaded

book

Article ID: 162383

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

Configuring RSA authentication fails with the error The file <C:\Users\Your_Username\Desktop\sdconf.rec> cannot be uploaded to the management server. This issue occurs after upgrading a Symantec Endpoint Protection Manager. 

ConfigSecurId-0.log shows the following error:

    2015-09-08 15:32:15.280 THREAD 79 SEVERE: SemLaunchService> getRequestTokenFromTokenMap>> requestTokens is null or empty, task name:ConfigureRSAAuth
    2015-09-08 15:32:15.280 THREAD 79 INFO: SemLaunchService> execute>> The request token is null. Task name: ConfigureRSAAuth

scm-server-0.log shows the following error:

    2015-09-08 15:32:15.280 THREAD 79 SEVERE:  in: com.sygate.scm.server.consolemanager.requesthandler.ConfigSecurIdHandler
    java.io.IOException: SemLaunchService: fail to config RSA login!
        at com.sygate.scm.server.consolemanager.requesthandler.ConfigSecurIdHandler.configWinRSALogin(ConfigSecurIdHandler.java:133)

 

Resolution

To resolve this issue, make the following changes to semlaunchsrv.properties. By default, this file is located in the folder C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc.

Note: Backup semlaunchsrv.properties before making any changes to the file.

If not present, add the following lines:

sem.launchsrv.exefilepath.taskname.RsaSecurId.sepm=tomcat\\bin\\securid.exe
sem.launchsrv.tokencount.taskname.RsaSecurId=1

If present, remove the following lines:

sem.launchsrv.tokencount.taskname.Msiexec=1
sem.launchsrv.tokencount.taskname.CommonCMD=1
sem.launchsrv.exefilepath.taskname.Msiexec.abs=msiexec
sem.launchsrv.exefilepath.taskname.CommonCMD.conf=scm.os.sysroot*\\cmd.exe